If your team spends hours copying information, chasing updates, maintaining spreadsheets or repeating the same administrative tasks, there's usually a better way. THACKR builds practical software and automation that removes repetitive work and gives your team more time to focus on customers.
Staff repeatedly enter the same information into different applications.
Managing everything in spreadsheets
Important operational processes rely on shared spreadsheets and manual updates.
Chasing customers
Your team manually sends reminders, requests documents or follows up on outstanding payments.
Creating documents manually
Agreements, reports, invoices or other documents are repeatedly generated by hand.
No clear view of progress
Information is scattered across emails, spreadsheets and multiple applications.
Repetitive approval processes
Requests and approvals involve unnecessary emails and manual tracking.
02What I can automate
Concrete examples of work that can be taken off your team
Customer onboarding and registration
Payment reminders and collections
Document generation and approval
Booking and scheduling workflows
CRM updates and synchronisation
Employee requests and approvals
Customer notifications
Reporting and operational dashboards
03Before and after
One process, with and without the manual steps
An illustrative example of the kind of change an automation sprint can make. It is not a guaranteed feature set: what is automated depends on your process and systems.
BeforeAfter
01Before: Customer submits a form.Customer
01After: Customer submits a form.Customer
02Before: Staff copy information into a spreadsheet.Manual
02After: Information enters the system automatically.Automatic
03Before: Someone manually creates an agreement.Manual
03After: Agreement is generated.Automatic
04Before: Customer receives an email.Manual
04After: Customer signs electronically.Customer
05Before: Staff chase the customer for payment.Manual
05After: Payment is collected through a secure provider.Automatic
06Before: Spreadsheet is updated.Manual
06After: Records update automatically.Automatic
07Before: Manager requests a status update.Manual
07After: Staff see progress in one dashboard.Automatic
04How it works
From messy process to a workflow that runs itself
01
Step 1: Understand the process
I map what currently happens, including the awkward manual steps.
02
Step 2: Find the opportunities
Identify which steps can be automated and where human decisions are still needed.
03
Step 3: Build and connect
Implement the agreed automation using existing software, integrations or custom development.
04
Step 4: Test and hand over
Test normal and failure scenarios, then show your team how to manage the new workflow.
05Pricing
One process, properly fixed
Final pricing depends on integrations, complexity and requirements. You'll have a fixed figure for an agreed scope before any work begins.
Business Automation Sprint
From £2,500
A fixed-scope project focused on improving one clearly defined business process.
Mapping of the current process
The agreed automation, built and connected
Testing of normal and failure scenarios
A handover so your team can manage it
Final pricing depends on integrations, complexity and requirements.
I don't automatically recommend building custom software.
Sometimes the most useful advice is that you don't need me to build anything.
1
Use what you already have
If an existing tool can solve the problem reliably, I'll recommend using it. You shouldn't pay for development you don't need.
2
Connect what you already have
Often the tools are fine and the gap is between them. A well-built connection is cheaper and lower risk than new software.
3
Build only where it earns its place
Custom development is for when it provides a genuine benefit, such as a process that doesn't fit off-the-shelf software or will outgrow it.
07FAQs
Automation questions
Can you work with our existing software?
Yes. Most automation projects build on tools you already use, connecting them through their APIs, webhooks or built-in automation features. I'll look at what you have first and only suggest new software if there's a real gap.
Do we need to replace our CRM?
Usually not. The aim is to make the CRM you have do more of the work, by keeping it updated automatically and connected to your other systems. If it genuinely can't support what you need, I'll tell you plainly, but that's the exception.
Can you automate spreadsheets?
Yes. Depending on the process, that can mean automating the data going into and out of a spreadsheet, generating documents from it, or replacing it with proper software when it has outgrown its job. I'll recommend the lightest option that works.
Can you integrate AI?
Where it helps, yes: sorting incoming enquiries, reading documents, drafting replies or flagging exceptions. It isn't the answer to everything, and plain rules are often more reliable, so I'll say which is which. A person stays in the loop for anything that matters.
What if our process changes?
Processes always change, so I build with that in mind, keeping the rules clear and documented rather than buried in code wherever practical. Small changes are usually quick to make afterwards, and anything larger can be scoped as a further piece of work.
How long does implementation take?
It depends on the process, the systems involved and how quickly access and decisions come back. A single, clearly defined workflow is usually a matter of weeks rather than months. I'd rather give you a real schedule once I've seen the process than promise a number now.
Will our staff need technical knowledge?
No. The automation should make the work simpler for them, not add a new tool to learn. Part of the project is showing your team how the new workflow behaves, what to do if it needs attention and who to contact.
Tell me which part of your business takes too much time.
When a vendor starts charging for an integration that used to be free, it exposes a risk that was there all along: you don't own the connection your business depends on.
A supplier outage is inevitable eventually. What matters is whether your software queues the work and carries on, or just fails in front of the customer.
A popular post can bring a wave of AI bot traffic that spikes your hosting bill and slows your site for real customers. Here's how to design for it before it happens.