Dates taken from each project's code history
How long a website or web app takes
From first code to public, these two builds took 6 days and 16 days. That clock leaves out any scope and design work before the code, so your whole project takes longer than this, and we'll put a date on yours in the written estimate.
What does that clock leave out?
Everything before the first code commit: the conversations, the written estimate and any design rounds. OnsiteOil's first code commit reads "implement product site from design handoff", so its design came before the code. It also leaves out everything after launch.
What makes a project take longer?
- Waiting on words and photos. A finished site with no copy can't launch.
- Slow decisions on the mockups. We don't take a deposit or start building until you've approved the design, so the build can't begin before you do.
- Other companies' systems. Moving a domain between registrars runs on the registrars' schedule. Payment accounts and email sending have their own setup steps too.
- The scope growing. Each change is priced first, and it adds time as well as money.
Does a bigger product just take longer?
Yes, and it may never fully finish. Plan a product with accounts, billing and outside systems as a first version, then a monthly retainer, and not as one long fixed-price project.
Can I get a date before I pay anything?
Yes. The written estimate covers scope, timeline and milestones, and it comes before the design work and the deposit.
Get a date for your project.
Tell us what you're building and when you need it. The first consultation is free, and you can also email info@ray-tech.io.
start_project()