Method
Each phase ends with something you own outright. A document, a system, a licence, a number. If a phase does not produce one, it has not finished.
- 012–4 weeks
Discover
We map the money, the rules and the constraints before anyone opens an editor.
Deliverable
Target architecture & regulatory path
- 023–6 weeks
Architect
Every interface, ledger entry and failure mode decided on paper first.
Deliverable
System design & threat model
- 033–9 months
Build
Small senior teams. Two-week cadence. Working software from sprint one.
Deliverable
Production system & test suite
- 044–8 weeks
Launch
Controlled rollout, live monitoring, a runbook for the night it breaks.
Deliverable
Go-live, runbooks, on-call
- 05Ongoing
Scale
New corridors, new licences, new volume. We hand over or we stay.
Deliverable
Roadmap & handover
The difference
Same brief, same budget. One of them is still going in year three.
How it usually goes
How we run it
- How it usually goesThe licence application and the build run as separate workstreams.
- How we run itOne plan. The system you ship is the system you described to the regulator.
- How it usually goesThe core ledger is picked on delivery speed and integration effort.
- How we run itThe ledger is designed first, because every product decision downstream inherits it.
- How it usually goesCompliance is a report written after the fact, to be shown at audit.
- How we run itScreening sits in the settlement path and fails closed. There is nothing to write up.
- How it usually goesA provider owns the rails, sets the pricing, and caps your margin.
- How we run itYou own the routing, the pricing and the margin. Nothing is rented.
- How it usually goesHandover is a document dump and a goodbye.
- How we run itHandover is continuous, and the people who built it are the people who ran it.
Common questions
How does a Valorifi engagement start?
With a Discover phase of two to four weeks, which maps the money flows, the regulatory path and the technical constraints, and ends with a target architecture and a costed plan. That document is yours whether or not the engagement continues.
Do you work alongside internal engineering teams?
Usually, and it produces better outcomes than working around them. The internal team holds context no external partner can acquire quickly, and they own the system afterwards. We structure engagements so knowledge transfer is continuous, not a handover event at the end.
What happens after launch?
Either we hand over against a documented runbook and a period of supported operation, or we stay to run the next phase. New corridors, new licences, new volume. That is a decision made at launch, not assumed in the contract.
Bring us the hard part.
Forty-five minutes with the people who would actually run the build.