Skip to content
Skip to content
CHIMBUK.

Try flutter, ai, pricing or sudoku

[04]Process

Predictability is a feature

How a project moves from first call to year-two support at Chimbuk — phases, pricing mechanics, quality gates, and the things we refuse to pretend about.

  1. 01

    Discovery & scoping

    Two workshops, one document. We map users, constraints and success metrics, then write the scope you'll hold us to.

    You bringHalf-days, honest answers, signed brief

    We deliverScope doc, risk list, fixed milestone plan

    1–2 weeks

  2. 02

    Design & prototype

    Flows before pixels: wireframes, then a clickable prototype in your brand (or ours, if you don't have one yet).

    You bringFeedback rounds — two included per artifact

    We deliverDesign system, prototype, accessibility pass (axe)

    2–4 weeks

  3. 03

    Engineering sprints

    Two-week sprints in your repos. Demo every sprint; staging from sprint one; change requests priced from a pre-agreed rate card.

    You bringSprint reviews, timely decisions

    We deliverTyped codebase, tests, CI with Lighthouse + axe gates

    4–16 weeks

  4. 04

    Launch & rollout

    Store submissions, analytics, monitoring, rollback plan. We've survived Play review before; your listing won't be our first rodeo.

    You bringAccounts & sign-offs ready (we'll checklist them)

    We deliverRelease runbook, store copy, 30-day hypercare

    1–2 weeks

  5. 05

    Support & maintenance

    Monthly retainer or hourly agreement: OS/SDK updates, dependency patching, crash triage, quarterly performance reviews.

    You bringA named contact, a shared inbox

    We deliverUptime-focused maintenance, change log, quarterly report

    Ongoing

How we price

  • Fixed-scope milestones

    Default for well-drawn projects. Each milestone is priced, dated and independently acceptable; changes are quote-first.

  • Monthly retainer

    For ongoing product work or maintenance: a reserved slice of the team, unused hours roll once.

  • Hourly, with a leash

    Advisory and small fixes at our standard rate — capped monthly so nobody's meter runs at you.

Quality gates — every release, no exceptions

  • Lighthouse CI ≥ 90 perf / 100 a11y / 100 SEO on key routes
  • axe-core automated pass + keyboard & screen-reader spot check
  • Type safety: strict TS, zod at every trust boundary
  • Store compliance pre-flight (Play policy checklist, privacy labels)
  • Rollback plan written before deploy, not after the incident
  • AI features ship with an evaluation set + cost model, or they don’t ship

Gates run in CI on every project that has CI. For one-off edits, the same bar is applied manually — and written into the change log you receive.

Things we won't do

No fake countdown timers. No “unlimited revision” traps that strangle quality. No bidding projects we can't staff — if your timeline needs six engineers and we're a studio of one-plus-circle, we'll say so and refer you onward. Losing the pitch honestly beats winning the project badly.

Begin the ascent

Start at phase 01.

Send the brief — we reply with questions, a milestone sketch and a yes/no on fit.

Start a project →WhatsApp