> For the full site index see https://www.fenwickautomation.com/llms.txt > Every page has a Markdown version at the same URL with .md appended. # Questions Every question people ask before, during and after a build, with the same answers you would get on the call: the audit, the price, who checks it. Answers to what owners ask before they book: the call, the build, what happens after it is live, and who we are. Every answer is the same one you would get on the call. ## Before you start **What happens on the 10-minute call?** The call is free. You describe the document that eats the most time. We say whether it fits and give a rough estimate: a range for the first route, not a quote. **We haven't got time to explain all this** The call is 10 minutes. After that, the audit needs your team for a handful of short sessions, and most of that is us watching how the job is done now, not you writing anything down. **What does the paid audit produce?** We look at the real documents and the real data, work out what the paperwork costs a year in your own figures, and write down what we found and what to build first. **What happens on the paid audit, in order?** First, a handful of short sessions with your team, most of them us watching how the job is done now. Then we look at the real documents and the real data: the quotes that went out, the templates, the spreadsheet that holds it together, and where the gaps are. From that we work out what the paperwork costs you a year, in your own figures, and write down what we found and what to build first. The fixed-price quote for the first route comes from that, with three options that cut scope rather than corners. **What do you need from us during the audit?** Your time, in a handful of short sessions, mostly spent showing us how the job is done now. The documents you actually send: recent quotes, the templates in use, one report that went out. Where the data lives and which fields are actually filled in. Where we need access to a system, we list exactly which before we start, read-only wherever possible, always through your own accounts. We sign a Data Processing Agreement before we see live data. **What if the audit says it is not worth automating?** Then we say so, in writing, and you do not get a quote. The audit still tells you what the paperwork costs you a year, which is worth knowing either way. We would rather lose a build than sell you one that does not pay for itself. **How much is the paid audit?** We give you the figure on the call, before anything is paid. **How is the build price set?** A fixed price for one route, from the audit, with three options that cut scope rather than corners. No day rates. **What makes a build bigger or smaller?** Five things move it: - How many different documents it has to produce. - How tidy your data is. Gaps get found in the data check, before we build. - How many systems it has to read from or write to. - How many rules change from one client or job to the next. - How much a person needs to check before anything goes out. You get a rough estimate on the call. The paid audit works out what the paperwork costs you a year. The fixed-price quote comes from the audit, with three options that cut scope rather than corners. ## The build **What does bespoke actually mean here?** Most automation is sold as a package, and you change how you work to fit the software. We go the other way. We map how your business works now, find where the time actually goes, and build the system around that. It runs on your rules, produces your documents in your format, and talks to the software you already pay for. The repetitive parts happen on their own. The parts that need judgement stay with a person. **What is the difference between the routes and the systems?** The routes are the shapes a build most often takes: Pipeline automation, Estimation, Lead qualification, Forms and documents, Automating CRM updating and Reporting. Each is sold on its own, built one at a time for a fixed price, and has its own page saying what it does, what it needs from you and what stays manual. The systems are narrower builds, each doing one job, such as chasing a quote or drafting a cold email. Some sit inside a route, some stand on their own. Neither list is a fixed menu. If a business does the same thing by hand more than once a month, it is a candidate. **Can you automate more than one thing at once?** We build one route at a time. The audit says which one pays back fastest, and that is the one that gets built first, for a fixed price. Once it is live and your team trusts it, the next one starts. Building two at once means two things half-trusted at the same time, and the parallel run only works when your team can compare one thing properly. **How long from signature to live?** From 4 weeks, depending on the size of the job. **What does it run on?** Every system we build runs on Claude. That is the only software we bring. You own the Claude Team plan and the seat the system runs on, in your name, on your bill. Keep paying for the seat and it keeps running. Remove the seat and it stops, the same as cancelling any software. Everything else is yours already, and it stays where it is. We do not ask you to change your job system, your accounts package, your spreadsheets or your inbox. We look at what you run today and build around it. **We already have software** Good. Keep it. We build on top of what you have, in accounts in your name. The problem is rarely the software. It is the gap between the software and the document someone still writes by hand. The system sits in that gap. **What will go wrong?** Your data has gaps. Two people describe the same rule differently. Somebody's spreadsheet is load-bearing. Version one will be wrong in a way only the person doing the job spots. The parallel run exists to catch all of that before go-live. **What do you not automate?** Nothing is fully automated where a mistake costs money or safety. A person checks anything that matters. That is the permanent rule, and it is why we turn down work from anyone who wants that last step removed. A system checks, drafts or assembles. It does not decide. It does not send a quote, sign a RAMS, or change a price on its own. Where it has no rule for something, it stops and hands that item to a person with a note saying why. ## After it is live **Does a person still check things?** Yes, anywhere a mistake costs money or safety. The system does the repetitive part and a person checks the output before it goes anywhere. **Who checks the output?** A named person on your side: whoever signs quotes off, whoever signs the RAMS, whoever reads the report before it goes to the client. The draft lands with them, with anything the system could not settle listed first. Nothing goes to a client or a site without that person seeing it. **How do we know it is working?** The parallel run. For as long as it takes your team to trust it, every job goes through twice: your team does it the way they always have, and the system produces its own version. Someone puts them side by side. The old way is switched off only when your team says so, not before. **What happens if it gets something wrong?** Version one will be wrong in a way only the person doing the job spots. During the parallel run that is expected, and it is why the old way keeps going beside the new one until your team says the output is right. After go-live, the person checking the output catches it before it goes anywhere, and the fix is part of the monthly running fee. **What does the monthly running fee cover?** Monitoring, fixes and small changes, so the system keeps running. It exists so that when something changes, it gets fixed rather than abandoned. **What happens when our rules change?** Rules change. A rate goes up, a client wants the price shown a different way, a new field appears on the job record. Small changes like that are part of the monthly running fee. Every rule the system follows is written down in the handover pack, so the change is made to a rule you can read, not to something hidden. **Can our team change it themselves?** Small things, yes. Wording, a price, a template line. We show your team how at go-live. Bigger changes go through us, under the monthly running fee. If you are not sure which a change is, ask and we will tell you. **We tried automation before and it didn't stick** Usually because it was built once, switched on, and the first time it was wrong nobody trusted it again. Every system we build runs alongside the old way first, until your team says it can stop. The monthly running fee exists so that when something changes, it gets fixed rather than abandoned. **Who owns the system at the end?** You do. Everything is in accounts in your name: the Claude Team plan and the seat, the logins, the documentation. You get a handover pack with every rule written down, and any competent developer can pick it up. **What happens if you disappear?** Everything is in accounts in your name: the tools, the logins, the documentation. Keep paying for the seat and it keeps running. Remove the seat and it stops, the same as cancelling any software. You get a handover pack with every rule written down, and any competent developer can pick it up. **Do you need access to our systems?** Some, and we'll list exactly which before we start. Read-only wherever possible, always through your own accounts, never through ours. We sign a Data Processing Agreement before we see live data. **Where is our data?** Where it is now. The system reads from the places your team already works in and writes back to them, through accounts in your name. We work through your accounts, never through ours, read-only wherever possible, and we sign a Data Processing Agreement before we see live data. ## Us **What size business do you work with?** We work with businesses from sole traders up to 25 staff. If yours is bigger than that, we're probably not the right fit, and we'll say so on the call. **What size business is too small?** None is, on size alone. We work with businesses from sole traders up to 25 staff. What matters is the paperwork: if the same document is done by hand more than once a month, there is something to build. **Do you work with businesses outside Kent?** Yes. We work remotely and can build for a business anywhere in the UK. We are based in Sevenoaks, Kent, and come to site if you ask. **Do you work with businesses outside construction?** Yes. We build for UK small businesses weighed down by paperwork. Construction is where the paperwork we know best comes from, and the rule is about the document, not the sector: any business that does the same document by hand more than once a month has something to build. Book the call and say what the document is. Last updated: 13 October 2026