Where the hours go
Supplier invoices re-typed into the ERP, step by step:
Hours per week, from what you tell us.

Home / Automation blueprint
A free, written automation blueprint for one process in your company: where the hours go, what to automate, what it's worth and a 4-week pilot plan. An engineer reviews every one.
See a sample blueprint (PDF) · Illustrative, for a fictional company
Sample cover. Yours carries your company name and your process.
Written for one process, in plain language, with the numbers shown so you can check them. Here are sample pages, shortened.
See a sample blueprint (PDF) · Illustrative, for a fictional company
Supplier invoices re-typed into the ERP, step by step:
Hours per week, from what you tell us.
Every option names the systems it touches.
≈ €26,220 a year
15 h a week × €38 an hour × 46 working weeks.
Illustrative example. Yours uses your hours and your cost.
Hours × cost, shown line by line.
Fixed price, agreed before we start.
If the honest answer is "don't automate this", the blueprint says that too.
No call needed to get the blueprint. A person checks it before it reaches you.
Which process eats your week, and your website.
Public information only: your site and your industry.
AI drafts. A senior engineer checks every recommendation.
English, Polish, German, French, Spanish or Italian.
30 minutes with the engineer who reviewed it.
An engineer checks every plan before it goes out.

Yes. There is no fee and no obligation. We write it because it is the fastest way for both sides to see whether automating your process is worth it.
Only what you send us and public information: your website and what is generally known about your industry. We do not log in anywhere and we do not contact your staff or clients.
Yes. We use AI to draft, and an engineer reviews every blueprint before it is sent. The engineer checks that the recommendations make sense for your systems and removes anything that does not.
Within a few hours of your request.
Then the blueprint says so, and explains why. Some processes are too rare, too varied or too cheap by hand to justify the work. Knowing that is useful too.
No. The blueprint ends with an option to request a 30-minute call with the engineer who reviewed it. You can also simply keep the plan.
We are an EU company in Poland and work GDPR-first.
You talk to the senior engineer who would build it, not a salesperson. Bring one process; we tell you plainly whether it's worth automating.