Seven stages
Every stage endswith somethingyou can inspect.
The work is divided by risk rather than ceremony. Each stage produces an output, ends with a decision you make, and can stop without making the previous work disappear.
The stages
- 01
Discover
We learn how your business works today, who will use the system and what it has to get right.
- Outputs
- Notes on goals, users, constraints and budget
- Decision gate
- Is this worth building, and are we the right team for it?
- Your involvement
- A conversation with the people who know the problem.
- Done when
- Both sides agree on the problem and the budget range.
- 02
Define
We write the scope: what is in, what is out, and how we will know it works.
- Outputs
- Written scope, acceptance rules and a fixed price per phase
- Decision gate
- You approve the scope and price before any build starts.
- Your involvement
- Review and sign off the written scope.
- Done when
- The important success and failure cases are written in testable language.
- 03
Architect
Decisions that are expensive to reverse are recorded with their cost, not just their benefit.
- Outputs
- Architecture and decision records
- Decision gate
- Hard-to-undo choices are agreed in writing.
- Your involvement
- Review the key trade-offs, explained in plain language.
- Done when
- Each expensive decision lists its cost, alternative and rollback path.
- 04
Build
Production code from the first commit: typed, migrated and tested, in your repository rather than ours.
- Outputs
- A running slice of the product in your repository
- Decision gate
- The slice works against real infrastructure.
- Your involvement
- See working software at every phase — not slides.
- Done when
- The slice passes its agreed checks.
- 05
Validate
The paths that carry money, identity and permissions get tests designed to break them.
- Outputs
- Test evidence for the acceptance and failure cases
- Decision gate
- Nothing launches with a failing critical check.
- Your involvement
- Try it yourself against the acceptance rules.
- Done when
- Money, identity, permissions and concurrency survive the cases designed to break them.
- 06
Launch
Deployment, documentation and a walkthrough with the people who will own it.
- Outputs
- Deployment, runbook and owner walkthrough
- Decision gate
- Your team can deploy and operate it.
- Your involvement
- A handover walkthrough with your team.
- Done when
- Your team can deploy, operate and change the system without TrinolIT.
- 07
Improve
Support after launch, then optional maintenance — monthly or task by task, with no required retainer.
- Outputs
- Fixes, improvements and a record of every change
- Decision gate
- Continue only while it is useful to you.
- Your involvement
- Tell us what to improve next.
- Done when
- Each change is tested and documented before release.
You can stop between phases and keep the work.
Larger builds are priced and billed by phase. Scope, code, decision records, tests and deployment live in your repository. A change to the price or outcome is written down before work continues, not explained on an invoice afterwards.
Put a problem through this processStart a project
Build somethingthat has to be right.
Tell us what you want to build and who will use it. You do not need a technical brief — a few sentences is enough to start.
- Or write directly
- hello@trinolit.com
- Where
- Dhaka, Bangladesh