Process
Six stages, and in each one you see something working
You pay per phase and accept each one working before paying for the next. Here is what we do, what you see and what you decide at every stage.
Why phases
Risk shrinks to one phase at a time
Agencies deliver at the end; freelancers deliver halfway; off-the-shelf software makes you operate its way. In all three cases you pay before you see. Here every phase is a block with a business goal, a date and a deliverable you see working with your own data. If you decide to stop at the end of a phase, you keep everything built, documented and in your name.
The six stages
What we do, what you see, what you decide
- 01
Operations review
- What we do
- A free 20-minute call to confirm the process and the decision-maker; then a 90-minute session with the person who decides and the person who runs it, a look at real files (spreadsheets, chats, forms), and a map of how it is done today.
- What you see
- A document with your current process in your team's words, what to automate first, later and not at all; an honest recommendation (custom, packaged, or nothing yet); and a phased proposal with a fixed price per phase.
- What you decide
- Whether to start phase 1, with whom and when. The document is useful with any provider.
- 02
Written definition
- What we do
- We write the scope of each phase, the business rules validated with you (price vs cost, credit limits, commissions, the odd case), the dates and what will be working at the end of each phase.
- What you see
- The product definition document and the phase plan. Anything not written is a change and is quoted separately; what is written is not renegotiated silently.
- What you decide
- The order of the phases. In the ERP DG it came from looking at the pasted-together spreadsheet.
- 03
Phases with a deliverable
- What we do
- Each phase starts with a deposit, has its own plan and ends in something you use.
- What you see
- The previous phase in production with your data while the next one is built. Never a demo at the end.
- What you decide
- Accept the phase, request one of the two included changes, or stop without penalty.
- 04
Building with tests
- What we do
- Every task is built with tests written before the code and reviewed before merging. One design system for every screen.
- What you see
- Weekly progress you can touch, in your team's vocabulary. Field tests where there is a route, a counter or a front desk.
- What you decide
- Which screen gets adjusted before closing.
- 05
Verification with evidence
- What we do
- A quality gate before closing each phase: clean build and unit, integration, database and browser suites green. The 'Requirements met' document maps each scope item to the screen where it is fulfilled and names what is missing.
- What you see
- The test count and the requirements document. In the ERP DG, the delivery run had 1,148 automated tests, including one that verifies inventory, cash, credit and profit reconcile with each other.
- What you decide
- Accept the phase and settle it.
- 06
Documented handover and evolution
- What we do
- We deploy on your accounts, import your real data, restore the backup into an empty database to prove it works, train by role and hand over the documents.
- What you see
- User manual inside the system, technical manual, requirements met, backup and restore guide, credentials outside the repository; and the 'what to automate next' list.
- What you decide
- Whether to reserve Continuous evolution so the system keeps up with the business month by month.
A real example with dates
How the Distribuidora del Golfo ERP was delivered
- Development started July 14, 2026.
- Six phases: core and catalog; warehouse, routes and point of sale; credit, collections and cash; purchases, costs and commissions; reports, alerts and audit log; offline mode, bulk import and backup.
- In production August 18, 2026, with 183 products and 8 categories imported from the client's spreadsheet.
- Delivery run on August 24: 1,148 automated tests (365 unit, 249 integration, 487 database, 47 browser).
- Six delivery documents and three batches of adjustments afterwards, requested by the client while using it.
- What stayed partial is named: 13 modules complete, 6 partial by agreement, 2 deferred in writing from day one.
What we need from you
Two hours a week and someone who decides
What delays a project most is client data and decisions. That is why the review asks for them first and the written definition names who decides within 48 hours. If there is no one today, we resume when there is.
How you pay
Payment follows the deliverable, not the calendar
Half when each phase starts; the other half when you accept it working. Two minor changes included per phase and 30 days of defect fixes after each handover. Anything outside the written scope is quoted as a change before it is done. No prices on the website: every proposal is calculated on your scope.
FAQ
Questions about the process
How many phases does a project have?
Four to six for a full system; a single one for an automation sprint or a website. Each phase lasts two to four weeks and has a written date.
What if I want to change something midway?
Each phase includes two minor changes. A scope change is written, quoted and decided before it is done; it never shows up on the invoice.
Can I see a system working before deciding?
Yes: a demo of the ERP DG with test data on the call, and the documented case under Work.
Which documents do I receive at the end?
User manual inside the system, technical manual, requirements met, backup and restore guide, credentials outside the repository. For the ERP DG it was six PDF documents.
Which technology do you use?
It is chosen for what your operation needs and explained in the technical proposal. The ERP DG runs on Next.js and Supabase, deployed on the client's accounts, with an installable app that works offline.
The first stage takes 20 minutes
Tell us how you run it today and we will tell you whether it makes sense to continue.