1. Home
  2. Process

Product Design & UI/UX

You always know what you're approving next.

KRIVA's five-phase process - discover, design, build, launch, and support - for product design, UI/UX, and development. Each phase has a written next step, a weekly demo, and a sign-off before we move on.

Book a free 20-min fit call→ Send a project brief→

Weekly demos Sign-off gates UK / US overlap Remote-first

Instrument Illustrative gates · no client data

KRIVA product design and development process

Who it's for

Founders and ops leads building trucking software, B2B SaaS, or finance integrations - who will join a weekly demo and sign a written brief before design or code starts.

What you receive

A scoped brief, signed UI pack, weekly working demos on a real URL, a go-live checklist, and an optional retainer path - each with a named deliverable and owner.

How we ensure quality

Hard sign-off gates before design and build. QA checkpoints in every build sprint. One decision-maker on each side. No phase starts on a handshake.

Same sequence for trucking consoles, SaaS products, and finance connectors. Capabilities under Services; stack under Tools & stack. AI-assisted development speeds work inside these phases - people still sign what ships.

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 and QA gates. Launch has a go-live checklist. Support is optional and named.

  1. 01

    Discover

    Goals, users, and constraints in a written brief you sign off.

  2. 02

    Design

    Flows, prototypes, and UI pack reviewed in weekly demos.

  3. 03

    Build

    Incremental delivery with QA gates on a live URL.

  4. 04

    Launch

    Deployment, handoff docs, and go-live checklist.

  5. 05

    Support

    Optional retainer for iteration and maintenance.

  1. W1–2

    Discover

    Phase 01 · 1–2 weeks You sign off

    Strategy, scope, users, constraints, and success metrics in a written brief. We sit with the desk that will use the product - often starting with UX research or workflow mapping, not only the sponsor who commissioned it.

    You leave with A scoped brief and a realistic timeline

  2. W3–7

    Design

    Phase 02 · 2–5 weeks You sign off

    Flows, prototypes, and high-fidelity UI reviewed in weekly demos. Product design and prototyping finish here - engineering does not start until the pack is signed. Changes after this gate are a change request, not a surprise.

    You leave with Clickable UI the floor can react to

  3. Weekly

    Build

    Phase 03 · weekly demos

    Incremental development with QA gates and open progress. You see working software every week on a real URL, not a big reveal. Regression checks run before each demo. Tools accelerate the work - a person still reviews what ships.

    You leave with Shippable increments, not a black box

  4. 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 with A live product and a named owner

  5. 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 with A clear retain-or-handoff decision

Cadence

How the week actually feels

Remote-first delivery, with overlap windows for UK and US clients so the demo is a conversation, not a recording.

01

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.

02

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.

03

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.

Most common

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→
Start here

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.

Book a free 20-min fit call →
Ongoing

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 →
QuickBooks QuickBooksOnline API Xero XeroCloud API

In practice

Three projects that ran these gates.

Same five phases on dispatch CRM, SaaS onboarding, and finance sync work. Browse all published work or read the cases below.

Trucking · Dispatch ShiftRail Written brief, signed UI, weekly demos, phased go-live beside the existing stack. Read case → SaaS · Onboarding PayrollPro Role-based onboarding flows designed and signed before build - first-run path shipped in weekly increments. Read case → Finance · Integrations FinanceSync QuickBooks and Xero connector with operator surface, QA gates, and a go-live checklist finance could trust. Read case →

Want the full picture? About KRIVA covers who we are. Tools & stack lists what we use inside these phases. Services is the capability catalog.

FAQ

About how we work

Straight answers so the first call starts further along.

Book a free 20-min fit call→

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 work remote-first. The studio is in 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.

Book a free 20-min fit call→ Send a project brief→

◆Reply within one business day ◆NDA on request ◆No commitment required