Skip to content
Zyntlow
Contact

Tell me what breaks.

The most useful first message describes the problem rather than the solution: what the business does, where the current system gives up, and what it costs when it does.

Response time
Within two working days
Base
Accra, Ghana
Timezone
GMT+0 · overlaps EU + US AM
Availability
Open to new work

Send a message

What to include

  • What the business actually does, in one paragraph.
  • Where the current system gives up, and how often.
  • Whether there is existing code, and who maintains it.
  • Rough timeline and whatever budget shape you have.

A few sentences is plenty. The four prompts above make the first reply a useful one instead of a list of questions.

Goes straight to the inbox that gets read. No list, no newsletter, no third party.

Engagements

01

Product engineering

Building a system end to end — schema, API, client, packaging and deploy. Most useful when the thing does not exist yet.

02

Architecture review

A platform that works but is getting harder to change. Offline strategy, multi-tenancy, data model, sync correctness.

03

Operational interfaces

Dense internal tools people use all day: keyboard-first flows, tables that hold up at scale, design systems that survive sixty screens.

Strongest ground

Offline-first architectureMulti-tenant data modellingProduct surfaces at scaleDesktop + web from one codebaseOn-device intelligenceMeasurement as a product

If you would rather not

Email
[email protected]
GitHub
@AdamsEugene

The form writes the message down before it tries to send it, so a provider having a bad day does not lose it. If it ever reports a failure, the address above reaches the same inbox.