Skip to content
diviteb

Engagements

Pick how we work together.

Five engagement models, one standard. Start small with a two-week discovery sprint, or bring us in for the whole build.

Start a projectHow we work

Engagement models

Five shapes. Change shape as you go.

Most clients start with a discovery sprint, move to a build, and keep a retainer after launch. Every model is quoted after a call — scope drives price, not a rate card.

  • Discovery sprint

    Two weeks to turn an idea or a mess into a costed, sequenced plan.

    Duration
    2 weeks
    Commercials
    Fixed price
    • Stakeholder workshops and a signed-off brief
    • Architecture sketch and risk register
    • A phased plan with effort estimates per phase
    • Yours to keep — build it with us, in-house, or with anyone else

    Best for: Scope is unclear, or you need a second opinion before committing budget.

  • Fixed-scope build

    A defined product, site, or system — shipped in milestones you can see.

    Duration
    4–16 weeks
    Commercials
    Fixed price per milestone
    • A dedicated senior team with one accountable lead
    • Working software demoed every two weeks
    • Milestone sign-off before the next one starts
    • Launch support and a documented handoff

    Best for: You know what you need and want a team accountable for shipping it.

  • Embedded team

    Senior engineers, designers, or PMs inside your sprints and standups.

    Duration
    Monthly, rolling
    Commercials
    Monthly per person
    • Named people up front — the same people stay through delivery
    • Works in your repo, your tracker, your rituals, on your roadmap
    • Pairs with your team by default, so the knowledge stays
    • Engineers, design engineers, or PMs; scale with a month's notice

    Best for: You have a roadmap and a team, and need senior capacity without a hiring cycle.

  • Retainer & support

    Keep what we built — or what you built — healthy and improving.

    Duration
    Monthly, rolling
    Commercials
    Monthly, sized to scope
    • Dependency, security, and platform updates on a schedule
    • Agreed response times for incidents
    • A monthly improvement budget you direct
    • Monthly report: what changed, what's next, what's at risk

    Best for: A product in production that needs upkeep, fixes, and steady improvement.

  • Advisory

    Senior judgment by the day — fractional CTO, reviews, and board prep.

    Duration
    Days per month
    Commercials
    Monthly, by days
    • A named senior advisor in your leadership rhythm
    • Architecture, vendor, and hiring decisions reviewed
    • Board and investor updates in plain language
    • Help hiring your permanent technical leader

    Best for: You need leadership-level technical decisions, not more hands on keyboards.

Common first projects

Eight places teams usually start.

Fixed-shape projects with a typical timeline and a concrete deliverable. Real timelines and pricing depend on the services you need.

Every engagement

Four things that never change.

  • Your repo, your cloud, from the first commit

    Code, infrastructure, and accounts live in your organization. We never hold IP or credentials hostage.

  • Senior people only

    The people on the sales call are the people doing the work. No bait-and-switch to a junior bench.

  • Working software every two weeks

    A demo you can click, on a preview URL, every cycle. Progress you can verify yourself.

  • A written update every Friday

    What shipped, what's next, what's at risk, and what we need from you — in one page.

Questions

What buyers ask us first.

Why aren't prices on the site?
Scope varies too much for a rate card to be honest. After a 30-minute call we send a written estimate within a few working days — a fixed price for defined scope, a monthly figure for embedded teams and retainers.
Can we start small?
Yes. A two-week discovery sprint is the usual first step. You keep the plan whether or not we build it.
Who owns the code and IP?
You do, from the first commit. Work happens in your repositories and cloud accounts, and IP transfers on payment.
What do you need from us?
One decision-maker who can give answers within a day or two, access to the systems in scope, and time from the people who know the problem.
Can we switch models mid-way?
Yes. Teams often move from a build to an embedded team or a retainer after launch. We agree the change in writing at the end of a cycle.

Next step

Tell us what you're trying to ship.

A 30-minute call with a senior practitioner. You'll leave with a recommended engagement model, even if it isn't with us.

Start a projectHow we work