Build timelines
Every project gets the same scoping, standards, and testing. You choose how fast we go: 100, 200, or 300 days. Faster means more of your team’s time. Slower means less back and forth.
01 / The plans
The difference is how much of your team’s time each one takes, and how the software reaches your users.
Suggested for you
The fastest route to launch. Best when you can give it real time now.
Suggested for you
A balance of speed and time commitment for teams with day jobs.
Suggested for you
A slower rollout with less back and forth. We batch our questions.
02 / Find your pace
Answer for your team as it is today. We’ll highlight the plan that fits, and we can adjust it together when we talk.
Our suggestion
0 of 3 answered
03 / How every plan works
The clock starts once we’ve agreed on the scope and everything we need from you is ready.
Before day 1 / Scope
We agree on the first release.
What it does, who it’s for, what waits for later, and which pace fits.
01 / Define
We work out the details.
Users, screens, data, and the systems it connects to.
02 / Build
We build and test it.
You review it as it comes together, on the rhythm your plan sets.
03 / Launch
It goes live.
All at once, with a pilot group, or in stages, depending on your plan.
04 / Project readiness
Every plan needs these before day 1. The faster the plan, the quicker we’ll need your answers.
05 / Questions
No. The scope we agree on is the same whatever the pace. A longer plan spreads the work out so your team spends less time on it each week.
Every project is a fixed price for the scope we agree on together. We quote it after a short paid scoping session, and that fee is credited toward your build. As a ballpark, most first releases land somewhere between $40,000 and $100,000, depending on what’s in scope.
Steady and Gradual cost about the same overall; Gradual spreads payments over more months. Sprint costs more because it needs more developers on your project at once. Sprint and Steady are paid as a deposit and then at each stage. Gradual is a deposit and then equal monthly payments.
If your project runs on a platform with its own subscription, such as Medplum, you pay that provider directly.
Yes, at the end of any phase. Speeding up depends on our availability and is priced on the remaining work. Slowing down spreads the remaining work over a longer schedule.
We phase it. We pick the part that’s most useful to launch first and plan the rest as later phases, each scoped on its own.
Ongoing support is a monthly plan with a set block of hours, sized to how much help you need. It covers fixes, small changes, and help keeping your system running. Larger additions are scoped as later phases.
No. Healthcare is our specialty, but every plan is open to any industry.
Tell us about the project and your team. We’ll suggest a plan on the first call.
Talk about your projectdev@codeduckers.com