Ten questions, and a scope you can forward

What this will not do

It will not give you a price. Anyone who quotes a workflow they have not seen is either padding heavily to cover the unknowns or is about to discover them at your expense. What it does instead is size the work against the one price ASTACKRA actually publishes — a fixed-scope AI sprint — so the number you get is anchored to something real rather than invented for the occasion.

It also will not flatter you. If your answers suggest the sensible move is to keep the tools you already have and build a thin layer between them, that is what it will say, even though it is the smallest piece of work on the menu.

Why the questions are the ones they are

• Roles and permissions predict complexity better than user numbers do. A system for five people with four different roles is harder than one for two hundred people who all see the same thing.
• Integrations are where estimates go wrong. Each system you must work with adds not just connection work but a decision about which side owns each field when they disagree.
• A system with no API is the single largest unknown any estimate can contain, which is why answering yes changes the shape of the plan rather than just the size.
• Whether a person must approve decides the architecture, not the interface. Binding output means audit trails, ownership and approval states designed in from the first data model.
• Constraints like data residency look like footnotes and are not. Naming a required region rules out hosting options and AI models before a line is written.

What happens with your answers

If you leave an email address, we keep a copy so we can pick up the conversation where you left it, and so we can see what people are actually asking for — which is how the studio decides what to build next. If you leave it blank, nothing is kept beyond the temporary document you download, which expires within a day.

Either way you are not added to a mailing list, and nobody will ring you.

If the shape looks right

Send the document to whoever needs to see it, then book a call and we will go through it, challenge the assumptions and tell you where we think it is wrong. If the shape looks wrong, say why — that is considerably more useful to us than a polite no.

You may also want the document sandbox, which runs a real tender or invoice through a live extraction pipeline in your browser, or the buy vs build comparison before you commit to building anything at all.