Skip to content
Curious Context Labs

how we work

Four steps. No surprises at the end.

Most projects follow four steps: we talk, we map the work, we build at a fixed price, and we keep it running. If the job is already clear, we can skip the audit and go straight to a build.

the protocol

From first call to a system your team uses every day

You can stop after any step. The roadmap from step two is yours to keep, whether or not we build it.

  1. Step 01

    Talk

    30 minutes, free

    You tell us how the business runs. We ask a lot of questions.

    • We ask where time goes, where errors creep in and where customers wait.
    • You leave with a few ideas, and an honest view on whether AI is the right fix.
  2. Step 02

    Map

    1–2 weeks

    We map the work and pick the use cases that pay off.

    • We interview the people who do the work and trace how it flows between tools.
    • You get a ranked roadmap and a fixed price for each build.
  3. Step 03

    Build

    Fixed price

    We build, show you an early demo on your data, and ship.

    • You see it working on real cases early, so there are no surprises at the end.
    • A person approves anything that matters before the AI acts on it.
  4. Step 04

    Run

    Monthly

    We monitor, improve and add new use cases.

    • We watch quality and cost, update models and fix issues.
    • We train your team and keep a backlog of what to automate next.

time zones

Working across time zones

Our team is in India. We work with businesses in the United States, the United Kingdom and Australia.

We keep fixed overlap hours for calls and reviews with each region: [OVERLAP HOURS]. You book calls inside that window, and it doesn't move around from week to week.

Much of the build work happens outside your office hours. For US clients that means overnight; for the UK and Australia our days overlap more. Either way, you regularly find something new to review: a demo, a fix or a short written update.

day --client=us-east
working / building overlap for calls: [OVERLAP HOURS] offline

before we start

What we need from you

Three things make the difference between an AI demo and an AI that does the work. None of them take much of your time.

  1. Access to the tools involved

    Logins or API access to the systems the AI will read from or write to, set up in your name. We document every permission we use.

  2. One person who knows the work

    Someone who does the job today and can spare an hour or two a week. They tell us how it really works, not how the manual says it works.

  3. Real examples to test on

    Past emails, invoices, tickets or documents, with anything sensitive removed if you prefer. We test on your real cases, not made-up ones.

promises

What you can hold us to

  1. Vendor-independent

    OpenAI, Claude, Gemini or open models — we choose per task, based on quality, cost and where your data may go.

  2. You own everything

    The code, prompts, data and AI accounts are yours. If we part ways, nothing is locked in with us.

  3. A person approves what matters

    Payments, customer promises, hiring decisions, anything legal: the AI drafts, a person decides.

  4. Fixed price before we build

    We agree the scope and price up front. If we underestimated, that is our problem, not yours.

Step one is a 30-minute call.

Tell us how the business runs and where work piles up. We ask questions, and you leave with a few concrete ideas or an honest answer that AI isn't the right fix yet.

Working with teams in the United States, United Kingdom and Australia.