Case studies
Problems we have solved for clients, with their names and anything that could identify them taken out.
Each one says what was wrong, what we did, how we checked it and what we did not do. Figures are rounded and some details are changed so that no client can be recognised.
One-off jobs
One fixed piece of work.
One-off job
Checkout stopped taking orders after an update
Customers could fill a basket but not pay. We found the cause on a copy of the shop, fixed it and proved it with test orders.
Online store · Two days
One-off job
Genuine payment messages were being rejected
Paid customers still showed as unpaid. The company's code was checking the wrong thing. We fixed it without switching the check off.
Software team · Three working days
One-off job
Questions the help centre did not answer
The support team answered the same questions every day, though a help centre existed. We ranked what was missing, out of date or hard to find.
Customer service · About a week
One-off job
A web form was creating duplicate contacts
The same person appeared twice, and one person's details were replaced by another's. We found why and fixed the one form that caused it.
Sales and marketing · Four days
One-off job
Former staff who still had access to company apps
People leave in one system and stay in the rest. We listed every leaver with a live account, with the evidence for each, and changed nothing.
People and IT · Five working days
One-off job
Security policies written from what the company does
A customer's security review asked for written policies. We wrote six short ones, and every sentence traces to something the company confirmed is true.
Security and compliance · One week
Monthly services
Something we keep working for you every month.
Monthly service
Supplier payment runs checked before they go out
A second pair of eyes on every payment run, with the evidence for each flag, so a duplicate or a changed bank detail is found before the money leaves.
Finance and back office · Ongoing, monthly
Monthly service
Builds that stayed red because nobody owned them
The main branch was red more than once a month and people had started merging past failing checks. Every failure is now investigated.
Software team · Ongoing, monthly
Monthly service
Checking the message sorter every month
A tool sorts incoming messages and drafts replies. Each month we test that it still agrees with the owner, and that nothing has been sent.
Sales and marketing · Ongoing, monthly
Projects
A bigger piece of work, bought as one result.
Project
Hundreds of products flagged in Google's shopping feed
Several problems at once, and every earlier fix had only revealed the next one. We grouped them by cause and worked through them in order.
Online store · Three weeks, mostly waiting for Google to reprocess
Project
A store's catalogue moved to Shopify and checked
Products, options and old web addresses all had to survive the move. We proved the import on a test store and compared the live shop with the old one.
Online store · Three weeks, to the launch date
Project
A supplier import rebuilt to stop bad files
A supplier's daily file had corrupted the catalogue more than once. We built a pipeline that checks every file and holds a bad one with reasons.
Data and spreadsheets · Six weeks
Full-time AI agents
An AI agent doing a whole role for you, every working day.
Full-time AI agent
A support team with a full-time AI agent
An AI agent works the help desk queue every working day, preparing replies and keeping the help centre current. A named person approves everything.
Customer service · Ongoing, monthly
Full-time AI agent
An AI software engineer working a product backlog
Features waited behind fixes and upkeep. An AI software engineer takes each request to something the founders can try, and they decide what ships.
Software team · Ongoing, monthly
We run it for you
A broad area of work we take on and run, under rules you set.
We run it for you
Engineering run as a service for a growing company
Nobody owned the whole job: intake, priorities, delivery, quality and upkeep. We took it on in steps, within limits the company set.
Software team · Ongoing, under a written agreement
What every case study tells you.
- What was wrong
In plain words, and what it was costing.
- What we did
In order, with the points where the client decided marked.
- How we checked it
The tests that had to pass before we asked for sign-off.
- What we did not do
The limits, so you know what the work does not cover.
Something like this?
You are asking about: a problem like one of these.
Sending this is not an order. We check we can help, then agree what is included, safe access and the price in writing before any work. Prefer email? hello@syntheticindustry.ai.