Stages, typical timelines and what you need to send
Every Gomes Code project follows five stages: conversation and scope, a prototype of the riskiest part, building with a preview link, documented launch and optional ongoing care. Price and timeline are agreed in writing before work starts.
The stages
Conversation and scope
Week zeroA conversation to find the real problem. You get a written scope with price, timeline and the list of what we deliberately agreed not to build.
The risky part first
Weeks 1 and 2Whatever could sink the project — an integration, data that may not exist, a hard business rule — is prototyped first. If it will not work, you find out while it is still cheap.
Building with visible progress
Until launchYou follow the project on a preview link, get a written update every week and see a demo every two weeks.
Launch and handover
At launchPublished with an automated deployment process and documented in plain language, including the parts another engineer may need to touch in the future.
Ongoing care
AfterwardsIf you want, we continue on a monthly plan: hosting, security, changes and ongoing development.
Typical timelines
Each project's timeline is set in the written scope.
| Project | Typical timeline |
|---|---|
| Data dashboard | 2 to 6 weeks |
| Full website or small system | 4 to 8 weeks |
| Custom system or large interactive | 6 to 12 weeks |
What you need to send
Websites
- Logo and brand colors, if any
- Copy or topics for each page
- Photos of the business, team or products
- Domain access (or the name you want to register)
- Contacts: phone, email, address and social links
Systems and dashboards
- How the process works today (a voice note or sketch is fine)
- Samples of current spreadsheets, reports or systems
- Who will use it and with what permissions
- The 3 to 5 numbers you most want to track
- One person to sign off each stage
Data projects
- The question the project should answer
- Available datasets or the public sources to use
- Publication date and outlet
- Style guide and credit rules
- Contact of the editor or approver
Tell us the problem. Reply within 1 business day.
Send the problem, not a spec.