Skip to content
FinHub

Approach

A discovery sprint first, then releases every two weeks.

How an engagement runs, from the first call to running the platform, and four ways to work with us.

The discovery sprint

Ten working days that end in a blueprint.

Fixed price, agreed before it starts. The blueprint is yours whether or not we build it.

Book a discovery call
  1. 1

    Days 1 to 2

    Kick-off and access

    We meet the people who own the product, the operations and the rules, and get read access to what exists.

  2. 2

    Days 3 to 7

    Map the product

    Systems, data flows, providers, manual steps and the checks a regulator or partner expects. Written down as we go.

  3. 3

    Days 8 to 10

    Blueprint and estimate

    Architecture, integration map, release plan, risks and a first estimate. Presented, discussed, then handed over.

  4. You leave with

    An architecture and integration map, a release plan with a first estimate, and a written recommendation. Build it with us, with your team, or with someone else.

The process

Four stages, four documents.

Each stage ends with something you can read, approve and share.

  1. 01

    Discovery sprint

    One to two weeks with your team. We map the product, the systems it touches and the rules it has to follow. It ends in a blueprint you can build with us or with anyone else.

    What you get

    • An architecture and integration map
    • A release plan with a first estimate
    • Risks, open questions and a recommendation
  2. 02

    Blueprint

    We turn the sprint into a written plan: what ships in each release, who does what, and what it costs. You approve it before work starts.

    What you get

    • A scope document you can share internally
    • A fixed price per release or a monthly plan
    • A named engineering lead
  3. 03

    Releases

    We build in short releases, each one demoed to you and reviewed by whoever has to sign it off. Compliance review time is in the plan from the start.

    What you get

    • A demo and a written update every fortnight
    • Working software in your own repositories and cloud
    • A decision and approval log
  4. 04

    Run

    After launch we keep the platform secure and moving, or hand it over to your team with documentation and runbooks. Either way, you own everything.

    What you get

    • Monitoring, patching and incident response
    • A monthly improvement plan
    • A handover pack whenever you want it

Engagement models

Four ways to work with us.

Every model starts with a written scope. We quote after a discovery call, because a price without a scope is a guess.

Discovery sprint

The first step for anything new.

A fixed-price sprint of one to two weeks that ends in a blueprint: architecture, integrations, release plan and estimate. Build it with us or take it elsewhere.

Best for

  • A new product or a major rebuild
  • A platform you are about to buy or invest in
  • An integration nobody has scoped yet
  • Deciding between vendors

How it works

  1. 01Kick-off call and access to your team and systems
  2. 02Interviews, system and data mapping
  3. 03Blueprint presented and handed over

Project build

A defined product or integration, delivered in releases.

We build what the blueprint describes, release by release, each one priced and signed off. Changes are re-quoted before the extra work starts.

Best for

  • An MVP or first version
  • A payment, banking or KYC integration
  • A marketing site and growth stack
  • A rebuild with a clear end state

How it works

  1. 01Blueprint approved
  2. 02Fortnightly releases with demos and sign-off
  3. 03Handover pack, optional managed engineering

Dedicated team

Named engineers on a monthly plan.

A set number of engineering days each month, planned against a roadmap we agree together. Run your platform, ship features, or both.

Best for

  • Running and improving a live platform
  • Engineering cover while you hire
  • A growing backlog of features and integrations
  • Ongoing site, search and analytics work

How it works

  1. 01Monthly plan agreed at the start of each month
  2. 02Fortnightly demos, monthly review
  3. 03Rolling agreement with a notice period

Fractional CTO

Senior technical judgement, part time.

A senior engineer in your leadership meetings, reviewing suppliers, vendors and plans, and leaving written recommendations. For businesses with builders but no technical lead.

Best for

  • Founders without a technical co-founder
  • Reviewing an outsourced team's work
  • Investor, partner or regulator technical questions
  • Choosing tools and vendors

How it works

  1. 01A fixed number of days or sessions per month
  2. 02Written notes after every session
  3. 03Email access in between
Comparison of the four engagement models
At a glanceDiscovery sprintProject buildDedicated teamFractional CTO
Pricing basisFixed price, agreed before the sprintFixed price per releaseMonthly fee for agreed engineering daysFixed days or sessions per month
CommitmentOne to two weeksUntil the agreed releases are acceptedRolling, with a notice periodMonth to month
CadenceDaily contact during the sprintFortnightly demos plus a written updateMonthly planning, fortnightly demosScheduled sessions plus written notes

Included in every model

Whichever shape you choose, these do not change.

  • A written scope before any work starts
  • A named engineering lead
  • Work in repositories and cloud accounts you own
  • A demo and a written update every fortnight
  • Compliance review time in the plan
  • Documentation and a handover pack whenever you want it

Working together

What a normal fortnight looks like.

A predictable rhythm and no surprises on the invoice.

A named engineering lead
One engineer owns the outcome and is on every demo and call.
A demo every fortnight
Working software, shown to you, with a written update you can read in two minutes.
Your repositories, your cloud
We work inside accounts you own. Part ways, rotate the keys, keep everything.
Review time built in
Compliance, security and partner reviews are scheduled into every release plan.
Decisions on record
Scope changes, approvals and open questions are logged where you can see them.
Honest scoping
If a request is a bad idea, or someone else would do it better, we say so first.

Book a discovery call

Bring us the product. We will bring the blueprint.

Tell us what you are building and what it has to plug into. A person replies within two working days.

Book a discovery callSee how we work