Switchgear manufacturer (name under NDA) · Low-voltage electrical panels · Italy
2 days
to a priced quote, instead of about 10
Quoted by hand. Then not.
3 weeks
UnblockSee the business
Unblock
The engineer was the system. We changed that.
One person holds the prices. Another holds the schedule. Orders live in email. When either of them is on holiday, the company stops quoting, booking or shipping. This is not a staffing problem. It's a structural one, and adding a feature on top of it produces a more sophisticated version of the same fragility.
What it usually looks like
- Quotes take ten days and depend on one engineer's memory.
- Homework, orders or bookings are checked by hand because the criteria exist only in someone's head.
- You already have a CRM. Nobody uses it, because it describes someone else's business.
- The director asks where a deal stands and waits for an answer.
What we do instead of the obvious answer
We write the criteria down. We put the formula in the system. We give each role exactly the screen it needs and nothing else. Where it helps, the system drafts and a person decides. Your ERP stays; we build what it doesn't do and connect the two.
Interactive
Days to a quote
| Before | After |
|---|---|
| 3–5 weeks | 1–2 days |
| 3–5 days | 2 hours |
| 3–5 days | under an hour |
| 3–5 days | 10 minutes |
Market context
76%
of engineers spend more than four hours a week on procurement and sourcing tasks.
Fictiv, State of Manufacturing 20258–10 h
a week teachers spend grading, in the UK and the US.
Learnosity, 2025
From the portfolio
Alfakom Learning Center · Education · International
3 → 1
three Telegram bots replaced by one app
The criteria were in the teacher's head. That was the problem.
2 weeks
Unblock
Talents Music School · Music education · Minneapolis, USA
0
manual payment calculations across 2 locations
They asked for a payment button. We looked at what they actually had.
Run it yourselfUnblock
Typically
A working pilot in days. A full system with roles, documents and dashboards in two to three weeks. Then support: fixes, answers, and the features you find you need.
Compliance by design
Where a system uses AI, we classify the risk, log every decision it proposes, document the data it uses and keep a person in charge of the outcome. You receive the technical file with the system. Your legal team gets answers before it asks.
Questions
Do you replace our ERP?
No. It stays. We build what it does not do, and connect the two.
What if our process changes?
It will. We build so the business can change rules, prompts and fields without calling a developer.
The system reads drawings. Is that safe?
Every line it proposes carries a reason and a reference to the source. A person confirms it before anything reaches a client.
What about the EU AI Act?
We build so your obligations are met by design: risk classification, decision logging, data documentation, human oversight, and a technical file delivered with the system.
Tell us what's missing.
Thirty minutes. You describe the pain and the result you want. We ask questions. If we can help, you get one email with what we found, what we'd build and what it costs. If we can't, we'll say so.