Scoping

Start with the problem, not the technology

You came here from Intelligence work, so we will start there. Four questions, then a straight answer about whether this is worth doing.

What we will ask

These are the questions a scoping conversation actually turns on. Answer them in an email and you have skipped a meeting.

  1. 01What is slow, manual or going wrong?The arc follows from the problem. We would rather hear 'we reconcile three till exports by hand every Monday' than 'we need AI'.
  2. 02How many people, and what do they already run?Tally, Zoho, Shopify, a WhatsApp group and four spreadsheets is a normal answer and a useful one. It decides how much of the work is integration.
  3. 03What is it costing you now?In hours a week or rupees a month. A number here is what makes the business case checkable instead of persuasive.
  4. 04What would you need to see to call it worth it?We write this down before the work starts and close against it at the end. Every story on /work does the same.

After you send it

What you get back, and when.

Within 2 working days

Which of the five arcs the work belongs to, and why — including if it is none of them.

With that reply

A published price band from /pricing with the assumptions that apply to you, not a custom quote.

If we have precedent

The closest client story we have. If we do not have one, we say so rather than stretching a different vertical to fit.

The AI scoping conversation is not live yet — it lands with the intake module. Until it does, this goes to a person, which is slower and, for a first conversation, mostly better. Nothing you send is used to train a model.

Send it to us