Straight answer first, from my own books instead of a brochure. The small stuff, one automation or one report or one connection between tools, has a median turnaround of five days from start to done. The mid-size tools, the quote builders and scheduling boards that run one part of a business, land around three weeks. And a full business system goes live a phase at a time, with the first working piece typically in your hands inside the first month.
Those numbers come from the record, not from optimism. Allen App Tools has more than a thousand paid jobs in its books. A hundred and seventy-nine of them are fixed-scope projects with clean start and finish dates, and the medians above are simply what those dates say. Some jobs run longer, and in a minute I’ll tell you exactly which ones and why, because that’s the part worth knowing before you hire anybody.
Why the calendar shrank
If you last priced a build years ago and remember quotes measured in quarters, both the price and the calendar have moved, and I’ve written about why. The short version: the expensive, slow part of software was always skilled hours, and one experienced developer working with AI now covers ground that used to take a small team. The machinery around a build moved too. Hosting, deployment, and the plumbing that once ate a week of setup is same-day work now. The build measured in weeks replaced the build measured in quarters.
Where the time actually goes
Here’s the part you only learn by doing this a few hundred times: the clock on a build runs on decisions, access, and examples more than on code. The code for a quote builder is a known quantity to a shop that has built quote builders. What stretches a job to double or triple its median is waiting: waiting for a login to the system we’re connecting to, waiting for a sample of the real spreadsheet, waiting for the owner and the office manager to agree on what “approved” means in their pipeline.
So the fast clients all look alike, and you can join them on purpose. They name one decision-maker. They hand over real examples on day one: the actual sheet, the actual invoice, mess included. And they answer small questions the same day they’re asked. Do those three things and the medians above are the timelines you should expect.
How the big systems ship
A complete operating system, the app your whole team logs into, follows a different rhythm on the same clock. It ships a phase at a time: each phase scoped, priced, and approved before it’s built, delivered in weeks, and working on its own. You run the business on phase one while phase two is being built. A fence and deck company’s system grew that way, and so did the app my own company runs on. The calendar total spans months, but the working software shows up near the start of it, and that’s the part that matters.
The honest caveats
Median means half were faster and half were slower. Integrations with slow-moving third parties add days. Migrating years of messy data adds days. December adds days. And a build can only start as fast as the calendar allows; a shop with a full queue should tell you so up front, and you should be suspicious of one that never has a queue at all.
If you’re reading this because you need something built soon, the useful move is a short scoping call, and it’s worth bringing the hiring questions to it. Tell me the job, and I’ll tell you which shelf it lives on, what that shelf honestly runs, and the real timeline with the caveats attached, including the possibility that a five-day job solves it. Speed in this trade comes from having done it before, and the books say we have.