One subscription, $2,995 a month, one active task at a time. This is the full list of what that covers, with the kind of thing people actually send under each heading. If yours is not on the list, send it anyway and I will tell you honestly whether it is a fit.
A whole application is not one task, it is a queue. We agree the shape up front, then it arrives in working pieces: auth and data model first, then the screens people use every day, then the reporting nobody thinks about until launch week. You see something running in the first weeks, not at the end.
Mobile apps
iOS and Android, native or cross-platform.
Cross-platform apps from an existing web product
App Store and Play Store submission
Push notifications, offline sync, deep links
Taking over an abandoned React Native codebase
A full app is a real project, usually months rather than weeks. You get an honest estimate before anything starts, and the build is split so there is a testable version on your phone early instead of a launch you cannot see coming.
Websites and e-commerce
Marketing sites, stores, memberships, rebuilds and migrations.
WooCommerce and Shopify builds and rescues
Marketing sites that load fast and rank
Membership and subscription sites
Platform migrations with URLs and SEO intact
A store is broken into catalogue, checkout, and everything that happens after the order. Migrations run alongside the live site until the new one is provably correct, so you are never cutting over on hope.
Usually the fastest wins on the whole list. Most of this lands inside a week: a deploy that stops being manual, a server that stops falling over, a page that stops taking nine seconds.
Integrations and automation
Connecting systems you already run so they stop needing people.
CRM, billing, and ERP connections
Payment and invoicing automation
Third-party APIs and webhooks
Removing recurring manual data entry
Scoped per connection. Two systems talking to each other is normally days, not weeks, and it is worth sending the ones that eat somebody's afternoon every week before the ones that sound impressive.
Fixing what is broken
Inherited codebases and software nobody else will touch.
Codebases left behind by a departed developer
Bugs three other people could not reproduce
Sites that broke after an update
Emergency recovery and clean-up
Send it even if you cannot describe what is wrong. The first pass is diagnosis, and you get a written answer on what is actually happening and what it takes to fix, before I start changing anything.
Security and audits
Reviews, hardening, and cleaning up after a compromise.
Security audits with a ranked fix list
Hacked site recovery and clean-up
Dependency and vulnerability upgrades
Access, secrets, and permissions review
An audit is one task and comes back as a prioritised list with severities, not a PDF you have to interpret. Fixing what it finds is the next task, and you choose how far down the list to go.
Best sent as the smallest useful version first. One workflow that works end to end beats a broad assistant that half works, and it tells you quickly whether the rest is worth building.
Data and reporting
Dashboards, exports, migrations, and the numbers behind them.
Reporting dashboards for non-technical teams
Database design and migration
Scheduled exports and reconciliation
Cleaning up data that stopped being trustworthy
The reporting question is almost always a data question first. Expect the first task to be getting the numbers correct and agreed, and the dashboard on top of it to be the quick part.
When the job is big
A four month build is not four months of silence.
Large work is split into tasks you can see land one at a time. That is what makes a monthly subscription safe to start: you are never more than a few weeks from something you can look at.
01
Shape it
You describe the whole thing, not a task list. I come back with the pieces it breaks into, in the order they should be built, and roughly how long each one takes.
02
Build the spine
The first piece is always the part everything else hangs off: data model, auth, the core flow. It goes to staging early so you are looking at something real.
03
Ship in slices
Each following piece is its own task, reviewed and tested before the next one starts. You can reorder the queue whenever priorities change.
04
Stop whenever
Because it ships in slices, you are never holding a half-finished build. Cancel after month two and you keep everything that shipped in months one and two.
Have something in mind?
Book a call and describe it out loud, or subscribe and send it today. Either way you get a straight answer on scope and timing before anything starts.
