Before we write a proposal, we make sure we understand what you need.
We get on a 30-minute call and ask how your business runs today and what you need. Then we write the proposal.
Six stages, scaled to the problem. Each one ends with something you can review, and during the build you get a demo every two weeks. We talk wherever your team already does: Slack, WhatsApp or email. The timelines below are for a full system. A well-built MVP takes a month or less, depending on complexity.
Before we write a proposal, we make sure we understand what you need.
We get on a 30-minute call and ask how your business runs today and what you need. Then we write the proposal.
Deliverables
Before we start, you know what we'll build and what it costs.
After we talk, you get the scope and price in writing: what goes into the first version and, just as important, what doesn't. We never start without an approved quote. If part of the work can't be estimated without a closer look, we propose a short first phase, priced on its own. The proposal is free.
Deliverables
You click through the screens before any code exists.
We design the key screens and walk through them with you before writing production code. In parallel we define the architecture, the data model and the integrations.
Deliverables
Two-week sprints with a demo at the end of each one.
We work in your repository from day one. Every change goes through code review and a preview environment with its own URL, so you can try it before it reaches production.
Deliverables
We go live with a rollback plan ready.
We migrate the data, set up monitoring and alerts, and stay with your team through the first days of real use. If something fails, we roll back to the previous version.
Deliverables
The people who built it maintain it.
After launch we look at how the system is used and prioritize improvements with you. We keep dependencies and security up to date so the system doesn't fall behind. If it goes down in production, we're on it as soon as you tell us, even if we're in the middle of other work. It's optional, billed monthly as a Maintenance plan.
Deliverables
We both know every project, and everything is documented. The code and access are in your name, so work keeps moving even if one of us is out.
We only take on a few projects at a time so we can deliver on each one. If we don't have room for yours, we'll tell you and give you a start date we can keep.
The code and data stay in your name, and we keep credentials in a password manager.
Three ways: a fixed-scope project, with a set scope, timeline and price; ongoing development, where we work as part of your team on monthly hours; or maintenance, for a system that's already live.
With a Maintenance plan, we're on it as soon as you let us know, even if we're in the middle of other work.
You keep the code, the access and the docs. It's all been in your name from the start, so another team can pick it up without needing us.
A well-built MVP takes a month or less, depending on complexity. The written proposal spells out the timeline.