Frequently asked questions.

No. There's nothing to log into and no seats to buy. A point solution ships the same product to everyone and leaves you to work out where it fits; CRFT couples human expertise to your context — your processes, your tooling, your rules, your goals — and builds the system that runs inside it. The output is a workflow that belongs to you, using whatever tools already earn their place in it. If a packaged product genuinely solves your problem, the honest answer is to buy the product, and the CRFT Scan will tell you that.

Forward-deployed. We embed with the people who actually run the workflow rather than working from a brief and returning with a system — because the thing that makes these work is context that never survives a requirements document: the exception everyone handles by hand, the reason step four exists, the spreadsheet that is really the source of truth. We sit in the workflow, demo weekly to the people doing the job, and hand over with the SOP and prompt kit so your team runs it without us.

It isn't SaaS — no license, no per-seat math, no renewal that costs the same whether the thing worked or not. Pricing is value-based and anchored to the outcome: we scope against the growth or operating number the workflow moves, publish a fixed price for the build, and put a guarantee on it. Ongoing capacity is optional and cancelable, and it scales on the system's complexity and the size of the team in the loop rather than on your headcount or ARR — the calculator shows your exact number before you talk to anyone.

Free discovery is a sales call — it ends in a proposal, not an answer. The CRFT Scan ends in a document you could hand to another firm: scored opportunities, quantified value, data-readiness levels, a defensible order of work. Half of what you pay credits straight into the build, so if you proceed it cost you nothing, and if you don't, you still own the analysis. Price your CRFT Scan here.

An agency builds what you spec but can't tell you what to spec — and it won't build the system to learn. A consultancy tells you what to do and leaves before anything runs. We do the diagnosis, the build and the support as one motion, at a published price, and we're accountable to a business number 90 days after launch rather than to hours or a deck.

No. The CRFT Scan Agents inventory every AI subscription you're paying for and show the overlap in dollars per month. Some tools earn their place and we integrate them; the ones you're renting at 100% for a 70% fit are the first candidates to replace with something built for how you actually work. Your CRM stays your CRM. Nothing is rip-and-replace.

Because we only build what the CRFT Scan already proved is worth building. Fit is confirmed before scope exists, the value target is the number you named, and the system reports its own results after launch — so there's nothing to argue about at day 90. If the build hasn't produced 3x ROI on its fee by then, we keep working at no charge until it does. If a CRFT Scan can't find 3x its own fee, we keep scanning.

CRFT Scan $2,500–$12,000. Production build $15,000–$55,000 fixed. Ongoing capacity $4,000–$16,000 a month, optional and cancelable — it scales on how complex the system is and how many people are in the loop, because a workflow two people touch and the same workflow across thirty are different amounts of work to keep running. We price on what the workflow costs you today, not your ARR or headcount — put your three inputs into the calculator and you'll see your exact number, credit and timeline without talking to anyone.

Almost everyone's is. The CRFT Scan scores readiness 1–5 per system and tells you plainly what has to be true before a loop can work. Sometimes the honest answer is that structuring one data source is the first build — and we'll say that instead of selling you an agent that quietly fails on bad inputs.

You own the system, the code, the prompts and the data it generates — outright, at handover. It ships with the SOP, prompt kit and launch playbook so your team can run it without us. Ongoing capacity exists because most clients want the loop to keep improving, not because leaving breaks anything.

No — and that's the main reason these hold up. Every build carries five disciplines: design (how the system talks to a person), change management (what happens to roles when a loop takes over a step), product (one outcome, ruthless scope, a version two), data science and engineering. A system is a living thing operating inside a human team, so we treat the handoffs, the trust and the process redesign as first-class build work rather than something the client figures out after go-live.

That's the failure mode we design against hardest. We sit with the people who run the workflow before we design it, demo weekly to actual users rather than stakeholders, and ship an adoption scorecard that measures whether the thing is being used — not whether it's deployed. If adoption stalls, that's our problem to fix, and it's visible to both of us in the tracker.