Cases
What we've built.
8to30 is a young company. We don't yet have client work we're able to publish, and we'd rather say that than fill this page with invented logos and testimonials.
The distinction
These are not client case studies.
What follows is our own work: systems we built ourselves, that run, and that we use. Showing them is the most honest way we have of demonstrating how we work while the first client projects can't be published.
When real client cases exist, they'll appear identified as such, with the client's name and their figures. Until then this distinction stays here at the top, not in a footnote.
In-house project
A system that chases quotes on its own.
It's the example that best sums up how we work, and not by accident: it came out of a problem we saw repeated in every company we spoke to. A quote goes out, the client doesn't reply, and nobody writes again — because chasing a month of open quotes by hand is a full day that nobody in a small company has.
Below it is in full: what it does step by step, what it's built on and how much time it compresses. It's also the basis for the priced service on the front page.
Quote reactivation system
The problem
Companies send quotes and never contact the people who don't reply. The quote sits in a spreadsheet and the sale goes cold without anyone deciding to let it go.
Stack
n8nGoogle SheetsGmail APITelegramAutomatic reply classification
What it does
- 01Reads the list of open quotes
- 02Decides who is due for contact based on days elapsed
- 03Sends a staged sequence of four messages, each with different copy
- 04Detects incoming replies and sorts them into interested, not interested or later
- 05Stops the sequence automatically as soon as someone answers
- 06Alerts the sales rep on their phone
The system doesn't close sales or replace the sales rep: it takes the chasing off them and leaves them the selling. When someone replies with interest, the conversation is human from the first message.
Standard
What we'll publish about each case.
Every future case will be documented the same way: the process before, the solution, the process after and the compression achieved in hours. If a project can't be measured like that, we won't publish it as a case.
The data structure already exists, so the first publishable case won't have to wait while we work out how to tell it.
- Client and sector.
- The problem, told the way the person living with it would tell it.
- Before and after, in hours.
- Annual time back and compression percentage.
- Tools used.
ClientSectorProblemBeforeSolutionAfterTime backCompression %ToolsResult
Want to be the first?
First projects are the ones that get looked after best. Tell us about your process.