/ 01 · Week 0–1
Diagnose
Code and architecture read, stakeholder interviews, and an end-to-end look at the system path. Output is written findings — the real bottleneck, not the symptom.
// about
Positioning built around what the register says we do.
Yezo Fintech designs and builds production software, and advises engineering teams on architecture and delivery. Every engagement maps to one of four registered activities — including management consultancy that explicitly excludes financial management. You know which activity you're buying, and what leaves the building at the end of it.
// how we work
Senior engineers only. Written findings. Production from the first increment.
Week markers below are the shape of a typical build engagement. Consultancy-only work usually stops at Blueprint.
/ 02 · Week 2
Blueprint
Target architecture, data model, delivery plan, risks and a cost envelope. Enough detail that another team could build it.
/ 03 · Week 3–10
Build
Two-week increments against your review process. Something reaches production in the first increment. Demo every second Friday, no exceptions.
/ 04 · Week 10+
Hand over
Runbooks, architecture decision records, on-call walkthrough and paired sessions until your team owns it. Retained capacity if you want it.
// registered activities
Four activities. One delivery team.
- Software developmentBusiness and domestic software development
Product platforms, transaction and ledger services, onboarding journeys, reconciliation tooling and back-office UIs — built for production, not as prototypes.
- IT consultancyInformation technology consultancy activities
Architecture reviews, integration strategy, platform and data decisions, and build-versus-buy calls for engineering teams.
- Management consultancyManagement consultancy activities other than financial management
Operating models, vendor selection, delivery organisation design, product roadmaps and process redesign — excluding financial management consultancy.
- Professional & technicalOther professional, scientific and technical activities not elsewhere classified
Technical due diligence, screening-vendor integration, reporting and data engineering, documentation and specification work.
// engineering standards
The five things we will not ship without.
These aren't preferences. In production transaction systems each one is the difference between a bad afternoon and a costly incident, so they're in scope by default.
- Ledger design
- Double-entry, append-only, immutable. Corrections are new entries, never edits — so the history stays defensible.
- Idempotency
- Every state-changing endpoint takes an idempotency key with exactly-once semantics and a documented retry contract.
- Reconciliation
- Treated as a product surface with owners and SLAs, not a nightly script nobody reads until something breaks.
- Keys & residency
- KMS or HSM-backed envelope encryption, documented key rotation, and data residency decided before the first table is created.
- Transaction observability
- Distributed tracing across critical paths, clear SLOs, and alerting that fires when balances or jobs go out of band.