Who this is for
Teams who want to see the next gate
Founders and ops leads who will join a weekly demo and sign a written brief before design or code starts.
- Home
- Process
How we work · Delivery
You always know what you're approving next.
Discovery, design, build, launch, and support. Each phase has a written next step, a weekly demo, and a sign-off before we move on. Tools help us move faster. People own every decision that ships.
Weekly demos Sign-off gates UK / US overlap Remote-first
Instrument Illustrative gates · no client data
Who this is not for
Services catalog or the tools list
What we sell lives under Services. Figma, Next.js, Make, and the rest live on Tools & stack. This page is how a KRIVA engagement actually runs — five phases, cadence, and three engagement models. Same sequence for trucking consoles, SaaS products, and finance connectors.
AI assists the work. A person still signs every decision that ships. That is also how AI-Assisted Development sits inside this process, not instead of it.
How a project runs
Five phases. Hard gates.
We do not start the next phase on a handshake. Discover and Design have hard sign-off. Build has weekly demos. Launch has a go-live checklist. Support is optional and named.
-
W1–2
Discover
Phase 01 · 1–2 weeks You sign off
Goals, users, constraints, and success metrics in a written brief. We sit with the desk that will use the product, not only the sponsor who commissioned it.
You leave withA scoped brief and a realistic timeline
-
W3–7
Design
Phase 02 · 2–5 weeks You sign off
Flows, prototypes, and high-fidelity UI reviewed in weekly demos. Engineering does not start until the pack is signed. Changes after this gate are a change request, not a surprise.
You leave withClickable UI the floor can react to
-
Weekly
Build
Phase 03 · weekly demos
Incremental delivery with QA gates and open progress. You see working software every week, not a big reveal. Tools accelerate the work. A person still reviews what ships.
You leave withShippable increments, not a black box
-
Go-live
Launch
Phase 04 Go-live checklist
Deployment, analytics, handoff docs, and training for the people who will run it. We do not call it live until the checklist is green and someone on your side can operate it.
You leave withA live product and a named owner
-
Optional
Support
Phase 05 · optional retainer
Iteration sprints, automation maintenance, and roadmap support. Most clients stay on a monthly retainer after launch. It is a choice, not a lock-in buried in the SOW.
You leave withA clear retain-or-handoff decision
Cadence
How the week actually feels
Ahmedabad, India. Remote-first. Overlap windows for UK and US clients so the demo is a conversation, not a recording.
Weekly demo, written next step
Every week you see the work and leave with the next decision named. No status theater. If a gate is blocked, we say so on the call.
UK and US hours, on purpose
Demos sit in the overlap. Async updates land in writing the same day. You are not expected to stay up for India midnight.
One owner on each side
You name a decision-maker. We name a lead. Feedback that is not from the owner waits. That is how sign-off stays real.
Engagement models
Pick the path that fits your stage
Same five phases. Different commitment. We will tell you if a full project is too early, or if a sprint is stalling a decision you already have.
Project engagement
6–16 weeks
Fixed scope with milestones, weekly demos, and a clear handoff. Design is signed before build. Launch has a checklist, not a hope.
Send a project brief→Discovery sprint
1–2 weeks
Align on scope, timeline, and what you actually need before a full engagement. You leave with a brief you can take in-house or bring back to us.
Request a fit call →Ongoing partnership
Rolling monthly
Iteration, design support, and automation maintenance after launch. Useful when the product is live and the roadmap is still moving.
Start a conversation →Same gates, different products
Dispatch consoles, SaaS MVPs, and finance connectors run this sequence
A QuickBooks or Xero engagement still gets a written brief, a signed design for the operator surface, weekly demos, and a go-live checklist. The APIs are original. The process is the same.
QuickBooks & Xero integrations →
QuickBooksOnline API
XeroCloud API
Discovery is 1–2 weeks. A full project is usually 6–16 weeks depending on scope. We will not quote a date until the brief is written. A fit call is for fit, not a fake timeline.
A named decision-maker, access to the people who will use the product, and feedback inside the weekly cadence. If the desk cannot join a demo, we will say the engagement is not ready.
We are remote-first from Ahmedabad, India, with overlap windows for UK and US clients. Demos sit in that overlap. Async notes go out the same day. You should not need midnight calls.
This page is the delivery sequence: phases, gates, cadence. AI-Assisted Development is how we use Claude, Copilot, and Cursor inside those phases. Tools speed the work. A person still signs what ships.
Yes. Finance connectors still get a written brief, a signed operator surface, weekly demos, and a go-live checklist. The write into QuickBooks Online or Xero uses the original APIs. The gates do not change.
You can take the handoff and run it, or stay on a monthly retainer for iteration and automation maintenance. Support is Phase 05 and optional. It is not bundled as a surprise.
Next step
Want to see how this fits your project?
A short fit call or a written brief. We will walk a realistic timeline and the first gate, not a pitch deck.
◆Reply within one business day ◆NDA on request ◆No commitment required