Answers

The questions you'd ask in the first call.

Plain answers about cost, timing, daily tasks and ownership, and three requests we turn down.

A — Cost and value

Questions about money.

What a system costs to build and run, and how to judge whether it is worth it.

“Will this be worth what it costs?”

It depends on how much time the task takes today, how much of it software can take over, and what the system costs to build and run. If software you can buy today does the job, we'll tell you which one. You get a first range for time and cost within two days of your brief.

Worth itDependson the task
Build costQuotedfor your project

“What does it cost to run after handover?”

Running costs depend on hosting, AI usage, any paid services the system connects to, and how much it is used. We estimate them separately from the build price for your project.

Running costsEstimatedfor your project
CodeYours
B — Daily tasks

Questions about daily tasks.

Email, approvals and reports: work your team repeats every week.

“Can software sort my email and draft the replies?”

Yes. The system sorts incoming messages and drafts replies on its own. By default, a person approves before anything is sent, paid or changed in your records. You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing. Unclear messages get a short summary and wait for review.

Routine messagesDraftedfor approval
Unclear messagesHeldfor review

“Can approvals move without me chasing people?”

Yes. Software can prepare reminders and show who needs to decide. By default, a person approves before anything is sent, paid or changed in your records. You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing. Large or unusual cases go to the responsible person, who decides.

Routine approvalsRulesyou choose
RemindersRulesyou choose

“Can the weekly report put itself together and check itself?”

Mostly. The system collects the figures and marks the numbers that don't match. A person reviews the differences and the explanation, starting from a suggested draft. A first working version takes 14–21 days from your confirmed brief; the exact date depends on scope.

Collect and compareAutomatic
Explaining differencesPersonreviewed
C — Systems and ownership

Questions about the systems underneath.

Document search, business apps and the records they use.

“Can answers quote our documents instead of guessing?”

Yes, for what your documents cover. Each answer links to the passage it uses. We test it on your own documents, including questions they don't answer, so you can see how often it finds the right passage and what it does when it can't.

AnswersLinkedto the source
Test documentsYours

“Can you replace the spreadsheet we track customers in?”

Yes. First we write down what the spreadsheet actually does, including the tabs only one person understands. Then we build the app around it. Moving your data and any time running both side by side are agreed in the scope.

Spreadsheet rulesMappedfirst
Moving your dataAgreedin the scope

“What happens when the AI gets it wrong?”

Sometimes it will. To limit the harm, the system records what it does, is tested on your own cases, and has limited permissions. By default, a person approves before anything is sent, paid or changed in your records. You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing. These checks lower the risk. They cannot catch every error.

ActionsRecorded
PermissionsLimitedby role
D — Questions we say no to

Three requests, three refusals.

  • “Build us a chatbot that sounds human.” — If the goal is to pass as human, that's a deception product. No.
  • “Automate the compliance sign-off.” — The signature carries legal weight. Software can prepare the records, reminders and checks; the signature stays yours.
  • “Just do a small pilot for the board.” — A trial needs an agreed task and a result to measure. Without one, we won't start it.