CloverityAI document processing

How we work

A transparent process, judged on business outcomes.

You should know what you are buying, what it will cost, and where it stands on any given day. So the work runs as a pipeline of six stages, and every one of them is a real exit point: you can stop after any stage and keep what was produced. Agreed outcomes and an agreed price before we start, visible progress while we build, and a system that keeps working after we hand it over — and if a date or an estimate is going to slip, you hear it from us the moment we know.

The process

From first conversation to a system in production.

Intro call → Discovery → PoC → MVP → Production → Support

Six stages. Every stage is a real exit point — you can stop after any stage and keep what was produced.

  1. 01

    Intro call

    What happens
    30–60 min. Your situation, not our pitch. We qualify honestly — if it's not a fit we say so.
    You walk away with
    A written summary of what we heard, plus a recommended next step (which may be “not us”).
    Exit decision
    Is there a real problem worth a paid discovery?
  2. 02

    Discovery

    3–5 days · $1,500–3,000 depending on scope

    What happens
    Paid, time-boxed: 3–5 days, $1,500–3,000 depending on scope. Requirements, goals, context, constraints, architecture. For larger products, we agree it individually at the intro call.
    You walk away with
    The full artefact package — yours to keep and execute with any team.
    Exit decision
    Go / no-go on build, with a realistic budget range in hand.
  3. 03

    PoC

    What happens
    The smallest slice that proves the risky assumption on your data.
    You walk away with
    A working prototype and an honest verdict on feasibility, including “this won't work” if that's the answer.
    Exit decision
    Does the approach actually hold on real data?
  4. 04

    MVP

    What happens
    The narrow first version a real user can use. Scope agreed at Discovery; the rest is explicitly post-MVP.
    You walk away with
    Working product, code, docs.
    Exit decision
    Does it deliver the outcome in production conditions?
  5. 05

    Production

    What happens
    Hardening, integrations, security, performance, rollout.
    You walk away with
    The live system, handed over with runbooks.
    Exit decision
    Ready to run it for real.
  6. 06

    Support

    What happens
    Ongoing maintenance, monitoring, iteration — reserved monthly days.
    You walk away with
    Agreed response expectations.
    Exit decision
    Renew or wind down.

What a Discovery actually produces

3–5 days · $1,500–3,000 · price agreed before we start

Discovery is the one stage most vendors skip and then pay for later. It is paid, time-boxed, and it ends with a package of artefacts rather than a proposal.

The artefact package

  1. Summary presentation — background, stakeholder map, requirements overview.
  2. Requirements — PRD and/or user stories.
  3. Architecture diagram plus a high-level plan and WBS.
  4. UX artefacts — core user flows and key screens.
  5. Budget as a min–max range, with a commitment not to exceed the top of the range.
  6. Communication schedule.
  7. Explicit handover list — what is transferred at each later stage.

You keep the artefacts either way — free to build with any team.

Nobody can give a defensible estimate on a non-trivial project without discovery; an estimate without it is a red flag about the vendor, not a favour.

For larger products, Discovery is scoped individually at the intro call.

Engagement

Pick the engagement that fits the job.

Different work carries different risk, and one commercial model cannot honestly cover all of it. So we offer three, and we will tell you which one your project belongs in — including when that is the cheaper one for you.

Fixed scope

Best for: Well-defined tasks — a prototype, an audit, one pipeline.

We agree on the outcome upfront, estimate each feature, and do our best to stay within 20% of the estimate. This works when we can both describe the finished thing before it exists — which is true more often than people expect, and we will say so plainly when it is not.

Discovery first

Best for: Bigger or fuzzier projects, where the shape is still forming.

A paid Discovery (3–5 days, $1,500–3,000, fixed price agreed upfront) produces the artefact package, a plan, and a priced proposal for the build. You keep the artefacts either way — if you decide not to build with us, or not to build at all, the analysis is still yours to use.

Dedicated capacity

Best for: Ongoing product work that will not finish and does not want to.

A monthly retainer of reserved days for features, improvements, and support. It is how we run our longest engagement today: a predictable amount of senior capacity every month, spent on whatever matters most that month.

On estimates. We estimate each feature upfront and do our best to stay within 20% of the estimate. That is a working promise, not a guarantee dressed up as one — and if something looks like it will break the estimate, you hear it when we find out, not when the invoice arrives.

Getting started

What happens next.

  1. You send a request

    Tell us the problem in your own words — the document type, the bottleneck, the thing that takes too long. No brief or specification needed.

  2. A free 15–30 min call

    We work out what you actually need and whether we are the right people for it. If we are not, we will say so on this call rather than three weeks in.

  3. A paid Discovery (3–5 days)

    We dig into the real documents and the real constraints, then come back with the artefact package and a priced proposal for the build. $1,500–3,000, fixed price agreed upfront.

You keep the artefacts either way. Even if you never work with us again, the Discovery output is yours — it is analysis you paid for, not a sales document.

Working together

How we communicate while the work is happening.

Most of what goes wrong on a project goes wrong quietly, in the gap between what you assume is happening and what is actually happening. We close that gap by default.

Regular updates

You get regular written updates on what moved, what did not, and what is next — in Slack or by email, whichever your team already lives in.

Direct access to the engineer

You talk to the person building your system, not to an account manager relaying questions. Technical answers come from the people who can actually answer them.

No middlemen

No layer of coordinators between your question and the work. Fewer people in the chain means fewer things lost on the way through it.

Working with your team

If you have engineers of your own, we fit into your tools and processes rather than importing ours — and hand over cleanly when the work is done.

Ready to see this on your own documents?

Start with the free 15–30 min call. Bring the document type that costs your team the most time, and we will tell you honestly what AI can and cannot do with it.

Start a conversation