Skip to content
diviteb

How we work

Ship in the open. Hand over everything.

One process across software, AI, marketing, and web. You see working software every two weeks, and nothing we build lives only in our heads.

Start a projectEngagement models

The process

Five phases. A written artifact at each.

  1. 01Week 0–2

    Discover

    We talk to the people who use, sell, and fund the thing. We read the code and the data. We write down what done means.

    • Brief with success criteria
    • Risk register
    • Effort estimate
  2. 02Week 2–3

    Plan

    We sequence the work into milestones small enough to demo. Every milestone has an owner, a date, and a definition of done.

    • Milestone plan
    • Architecture decision records
    • Test strategy
  3. 03Two-week cycles

    Build

    We ship to a preview environment from the first week. You see working software every two weeks, not slides.

    • Demo every two weeks
    • Written update every Friday
    • Preview URL per change
  4. 041–2 weeks

    Launch

    Staged rollout, monitored, with a rollback rehearsed before launch day. We stay on through the first production weeks.

    • Launch checklist
    • Rollback runbook
    • Monitoring and alerts
  5. 05Ongoing

    Hand off or operate

    Your team takes over with docs and runbooks — or we stay on a retainer. Either way, nothing lives only in our heads.

    • Runbooks
    • Architecture docs
    • Access transferred

The rhythm

A week you can set your watch by.

We work in your tools — your repo, your tracker, your chat. You never chase us for status; it arrives in writing.

  • MonPlanPriorities agreed with your decision-maker.
  • DailyAsync standupWritten, in your Slack or Teams.
  • Every other WedDemoWorking software on a preview URL.
  • FriWritten updateShipped, next, risks, and asks.

The quality bar

Done means tested, accessible, and documented.

  • Type-checked, linted, and tested in CI on every pull request
  • A preview deployment for every change
  • Accessibility to WCAG 2.2 AA, checked by tools and by people
  • Performance budgets that fail the build when exceeded
  • Security review for anything touching auth, payments, or personal data
  • Architecture decisions written down, with the alternatives we rejected

  • Day 1

    Code in your repo and cloud accounts

  • 2 wk

    Between demos of working software

  • Fri

    Written update, every week

  • All

    Code, docs, and access handed over

Questions

What buyers ask us first.

Do you work in our tools or yours?
Yours. Your GitHub or GitLab, your cloud accounts, your Jira or Linear, your Slack or Teams. We bring opinions, not a separate system to log into.
How involved do we need to be?
Plan on one decision-maker for about two hours a week, plus the demo every other week. Faster answers mean faster delivery.
What happens when the project ends?
You get runbooks, architecture docs, and a recorded walkthrough, and all access is already yours. If you want us to keep running it, that becomes a retainer.
How do you use AI in delivery?
We use AI coding and research tools where they speed us up, with every change reviewed by a senior engineer and covered by tests. We never send your confidential data to a model provider without your written approval.

Next step

See it on your project.

A 30-minute call. We'll sketch the first two weeks of the work before we hang up.

Start a projectEngagement models