Accra, Ghana · Independent engineering organization · Est. 2023
Zyntlow is the engineering organization of Adams Eugene. TallyhubGH, Kernvo and Tresoria Beauty are live in production today; 22 more projects have been built since 2023 across commerce, field operations, health, analytics and developer tooling. Offline-first, multi-tenant, and built to survive a bad connection.
Everything below is running in production. The numbers are counted from the source, and the links go straight to the real thing — no demos, no waiting list.
A multi-tenant commerce platform that keeps selling when the internet stops — offline-first POS, warehouse-scoped inventory, credit sales, purchasing, reporting and on-device AI, shipping as web app, installable PWA and desktop binary from one codebase.
Core banking built around a real double-entry general ledger: the customer officer, the cash desk, the loan book and the accountant all write to the same books, and the books are never allowed to be out of balance.
An online store for a Kumasi hair brand — premium extensions, wigs, accessories and care products — with mobile money as the primary way to pay, honest delivery pricing quoted before checkout, and an admin dashboard the owner runs the shop from without a developer.
Most business software is written on the assumption that a request will succeed. In a shop in Accra with intermittent power, a shared counter device and a queue of customers, that assumption is a bug. A till that refuses a sale because a socket dropped is worse than no till at all.
So every product here starts from the opposite premise: the device is the source of truth, the server is eventually consistent, and every write is designed to be replayed safely. That constraint produces software that is faster and more reliable everywhere — it just happens to be non-negotiable here.
Same engineering, pointed at your problem. If none of these is quite it, describe the problem and I will tell you honestly whether I am the right person for it.
End to end: data model, API, client, desktop packaging, deploy pipeline. Most useful when the thing does not exist yet and needs to be right the first time.
Best fit: a founder or business with a clear operational problem and no system for it.
Local-first storage, replay queues, idempotent writes, deterministic conflict rules. The difference between software that survives a dropped connection and software that loses a day of trading.
Best fit: point of sale, field operations, anything used where connectivity is not guaranteed.
Dense operational screens: keyboard-first flows, tables that hold up at scale, loading states designed rather than bolted on, a design system that survives sixty screens.
Best fit: an internal tool your team fights with every day.
A platform that works but is getting harder to change. Multi-tenancy, sync correctness, data model, the seams where the next six months of bugs are hiding — written up, with a plan.
Best fit: a product past its first version, before the rewrite conversation starts.
Eight domains, one engineering practice. The hard problems repeat inside a domain and rarely across them, which is why the work is grouped this way rather than by year or client.
Point of sale, inventory, and the ledgers underneath them.
Accounts, ledgers, transfers, and the screens that expose them.
Software that has to work where the network does not.
Records, scheduling and care pathways.
Measuring what visitors do, then changing it.
Sharpening the tools that build everything else.
Courses, cohorts, and school administration.
Booking, ordering and community apps for local businesses.
Client sites taught delivery. Analytics work taught measurement. Commerce taught what happens when software is load-bearing and a shop cannot trade without it.
Client and community work — laundry, school and teaching tools — alongside the browser experiments and Chrome extensions that became a habit of building small, sharp utilities.
Deep work on behavioural analytics: heatmap filtering and benchmarking, comparison filters, page-vitals instrumentation, and the first site graders — including an AI-assisted version.
The portfolio shifts from sites to systems: hospital management, e-learning with a separate API, the Halo widget and plugin runtimes, StockFlow inventory, and the beginnings of TallyhubGH.
TallyhubGH becomes a full commerce platform — offline POS, Tauri desktop, on-device AI, billing — and goes live at tallyhubgh.com. The banking work built as Franlind ships as Kernvo at kernvo.com. Tresoria Beauty opens a mobile-money storefront for a Kumasi hair brand at tresoriabeauties.com. Farm Ops, MamaCare, Frontdesk, MarkFlow and Canvas Studio follow. Zyntlow becomes the name over all of it.
Remote-first, GMT+0, overlapping with Europe for a full day and the Americas for half of one. The same codebases run on a counter in a market and in a browser tab anywhere else.
Tell me what the business does and where the current system gives up. You will get an honest answer about whether I can help, and how I would approach it — not a pitch.
