Skip to content
Desmok AI

SHT 07 · PROCESS · REV A

How we work: five steps, no black boxes

A short discovery, a fixed proposal, a build you watch every week, a clean launch, and support after.

No open-ended billing. Working software, every week, until it's live.

Start a projectSee the three offers

SEC 02 — TIMELINE

The timeline: first call to production

Each step ends with something you can hold — a document, a demo, a deployment.

  1. DAYS 1–3

    Step 1: Discover

    Every project starts with a working session, not a sales call. We define the problem in plain terms: who it's for, what it must do, and what "done" looks like.

    WHAT HAPPENS

    • A structured working session with the engineers and designers who will build it.
    • We map the problem space: users, workflows, systems, constraints.
    • We flag risks early: data availability, integrations, compliance, unknowns.

    YOUR SIDE

    Bring the person who owns the problem. One or two sessions of 60–90 minutes.

  2. WEEK 1

    Step 2: Scope

    Within the first week you receive a fixed proposal: features, architecture, timeline, and price. Not a range — a number. It states what's in, what's out, and where each milestone lands.

    WHAT HAPPENS

    • The discovery output becomes a concrete build plan: features, architecture, stack, milestones.
    • A fixed quote tied to milestones. No open-ended billing.
    • We agree what's explicitly out of scope, so scope creep has nowhere to hide.

    YOUR SIDE

    Read it, challenge it, decide. We revise once, or you keep the plan and walk away.

  3. BUILD PHASE

    Step 3: Build

    Weekly demos of working software. You steer priorities between milestones and talk directly to the engineers writing the code. Version control, CI/CD, staging, and evals on AI features from day one.

    WHAT HAPPENS

    • Weekly demos of working software, on a call, on a fixed day.
    • A shared channel with the engineers and designers on your project.
    • Sign-off milestones, and billing follows those sign-offs.

    YOUR SIDE

    Thirty minutes a week for the demo, plus timely answers in the shared channel.

  4. FINAL WEEK

    Step 4: Launch

    Launch is a checklist, not a leap of faith. We deploy to production, run QA against the success criteria from step one, and hand over everything: code, credentials, and documentation.

    WHAT HAPPENS

    • Production deployment with monitoring, logging, and alerting configured.
    • QA against the agreed success criteria, plus a security review of auth, secrets, and access.
    • Full handover: repository transfer, credentials, and a walkthrough with your team.

    YOUR SIDE

    Provide production accounts, or ask us to set them up in your name. Attend one walkthrough.

  5. ONGOING · OPTIONAL

    Step 5: Support

    Launch is the start of learning what users actually do with the product. An optional retainer keeps the team that built it on call — optional, because the handover is real.

    WHAT HAPPENS

    • Monitoring and alerting continue from day one in production.
    • Maintenance and fixes under retainer or on demand.
    • A roadmap session after the first weeks of real usage.

    YOUR SIDE

    Decide whether you want a retainer, your own team, or a mix.

This is the same spine behind every offer — see how it flexes for MVP-to-Launch, AI Automation, and AI Integration.

SEC 03 — GROUND RULES

Ground rules

Six commitments that apply to every engagement, from the first call.

R-01

Fixed quotes

The price in the proposal is the price you pay for the scope we agreed.

R-02

Milestone billing

Invoices follow delivered, signed-off milestones. You pay for working software, not elapsed time.

R-03

Weekly demo cadence

Every week you see the real product running.

R-04

Direct line to the builders

You talk to the engineers and designers doing the work.

R-05

Your IP, always

Code, designs, documentation, and infrastructure are yours from handover, transferred in writing.

R-06

NDA-friendly

Happy to sign yours before the first call.

No black boxes, no status-report theatre.

OPERATING PRINCIPLE · EVERY DESMOK AI PROJECT

SEC 04 — WHAT YOU GET

What you get, step by step

The whole engagement on one sheet.

STEPARTIFACTSOWNER
01 DiscoverShared problem definition · candidate solution outline · open-questions listYours to keep, even if we never work together
02 ScopeFixed proposal (features, architecture, timeline, price) · milestone map · workflow audit (automation projects)Yours to keep, either way
03 BuildLive staging build · weekly demo recordings · written changelogs · milestone sign-off recordsYours — visible throughout, transferred at handover
04 LaunchProduction deployment · full codebase in your repos · CI/CD pipelines · docs (architecture, runbook, API) · written IP transferYours, in writing — code, IP, infra, credentials
05 SupportOptional retainer agreement · post-launch roadmap · monitoring & alerting in your accountsYours — retainer optional, exit always clean

"Yours to keep either way" is literal — the discovery output and the fixed proposal have no strings attached. That's the free scoping step of how every engagement starts.

NEXT STEP

Start at step one

A free 30-minute intro call, then a build plan or automation audit. You'll know within a week what we'd build and what it costs.

Book the intro callOr read the three offers first

Fixed quote before any commitment. NDA-friendly from the first conversation.