Custom software for intake, work queues, assignment and client communication — built by an engineer who has run one for 10 years.
Briefs arrive by email, Slack and WhatsApp; nothing lands in one queue.
Someone decides who takes each request, every time, by hand.
Clients ping for status because they can’t see it.
CRM + Asana + Sheets + invoicing, each charging per seat, none built for your workflow.
Illustrative — the real one is shaped around how your shop runs. One queue, automatic dispatch, and a status page clients check instead of pinging you.
How requests come in, who dispatches them, where hours leak. Free, and useful even if we never work together.
A scoped proposal for the one workflow that removes the most busywork — nothing you don’t need.
I build it, put it in front of your team, and keep it alive for years — like the one running since 2015.
Probably — I ran the platform behind a productized creative service for 10 years, so intake, dispatch and client communication are home turf. But the process doesn’t assume a vertical: every engagement starts with a free audit of how your shop actually runs, and the proposal comes from that, not from a template.
There’s no package price because there’s no package. The audit is free, and the proposal that follows is scoped and priced for your specific workflow, so you see the number before any code is written. I’ve also published honest price ranges →
The audit comes first. A thin, useful first version — usually the intake queue — typically ships within a few weeks after that, and we grow it from what your team actually uses.
Yes. The code, the data, the infrastructure accounts — all yours, from day one. If we ever stop working together, everything keeps running and any developer can pick it up.
Yes — two-way sync is a specialty. The platform in the proof section synced with Trello for years so clients never had to leave it. Integrations with the tools you already use are usually part of the first version, not an add-on. See how I build integrations →