Stop guessing about what technology would actually help.

No. The audit works just as well on how one person's week runs as it does on a company's operations. Employees, freelancers and people managing personal projects are all in scope.

No, and you are not expected to. Working out whether AI is even the right answer is part of what the audit does. Describing what you are trying to improve is enough.

Technical terms appear only where they genuinely help, and the plain explanation always comes first. You would read “a searchable assistant that answers questions using your own documents”, not “an LLM-based RAG pipeline”. The technical name is there if you want to look it up, never in place of the explanation.

Often, yes, and each recommendation says so directly. Where something is realistically a configuration job you can handle, the audit says that and gives you the first step. Where it genuinely needs help, it says that too. The balance depends on your situation; no change is a valid conclusion.

A structured questionnaire covering what you want to accomplish, how you handle it today, what takes too much time, which tools you use, and any constraints. It is written in plain language and needs no technical write-up.

Fifteen minutes, scheduled after your audit has been delivered so you can read it first. That is deliberate: arriving already familiar with the recommendations is what makes a short call useful.

Yes. Research, organization, recurring admin, learning, project management and getting your existing tools working together are all legitimate subjects for an audit.

Yes, at a directional level: whether custom development is warranted, whether an existing tool already solves it, whether a website is sufficient, what a first version might contain, and what order to build things in. It is not a detailed technical specification or a full architecture document.

Where a specific tool genuinely fits, yes, and it is named. Where the software you already own covers it, the audit says that instead. Sometimes the recommendation is to change nothing at all.

Yes, if you want that. Implementation is scoped and quoted separately as a Workflow & System Design or a Custom System Build, and builds are covered by the Build Guarantee. It is a separate decision, made after the audit.

While you fill in the questionnaire, answers stay in this browser, with a local recovery copy where browser storage is available. When you continue to checkout, your answers are stored on our server before Stripe opens. They enter human review only after payment is confirmed. Unpaid server records become eligible for deletion after 7 days; a payment still processing has a 30-day window, and a failed payment has a new 7-day window. Expired records are removed when the next successful questionnaire submission runs cleanup, so deletion is not guaranteed on the expiry date. Paid records are excluded from that cleanup. Browser recovery copies expire when next opened after 30 days or can be removed by clearing site storage. Filling in the questionnaire does not commission an audit.

Your answers are stored on our server before checkout opens. A browser recovery copy also helps you return to the form where storage is available. Once paid, fulfillment does not depend on your browser or on returning from Stripe.

Yes. The audit is yours. Give it to your own team, your existing developer, or another provider if that suits you better.

It is not a complete systems architecture, an engineering specification, a security audit, a CRM migration plan, implementation, unlimited consulting, financial modelling, legal advice, or a full business strategy engagement. It is a prioritized opportunity assessment and a practical starting plan.