For businesses where software is a tool, not the product
Take the repetitive work off your people.
Most companies have a spreadsheet everyone depends on, an inbox sorted by hand, or quotes typed from PDFs. We spend half a day with the people who do that work and tell you, in writing, which of it is worth fixing and with what. Sometimes that's AI. Often it isn't.
A short conversation, in person, by phone, or by video. No preparation needed from your side, but you can show us the spreadsheet if you like. You leave with a straight answer, even if the answer is "leave it as it is".
Sounds familiar?
Every spreadsheet that runs a business started as a quick fix. It worked, so it stayed. A few years later, it looks like this:
Nobody trusts the numbers
There are two reports and two totals for the same month. Someone reconciles them by hand and picks the one that looks right. The decision gets made on a number nobody would sign.
Only one person knows how it works
One colleague built the sheet and is the only one who knows why column AF matters. When they're on vacation, the report waits. When they leave, the knowledge leaves with them.
Friday afternoon pain
Every week someone copies data from one file into another, repairs the broken references and sends the report at six. That's half a working day every week spent moving numbers instead of using them.
One renamed header, three broken files
Someone renames a header or inserts a row, and three other files quietly go wrong. Nobody notices until month-end, or until a customer complains.
40 emails before 10:00
Every morning, someone reads forty emails, calls the same five suppliers, files the invoices, and answers the same three questions about shipping. By ten they start the actual job.
Data typed in by hand
Orders arrive as PDFs and emails, and someone types every line into the system. Every line is a chance for a wrong quantity, and the customer notices it before you do.
The tools did their job for years, and the business grew past them. We take that work off your people and give them a system that does it the same way every time. Your people get their time back for better things, and the colleague who does the work today is usually the best person to shape what replaces it.
You're dealing with a person, not a faceless agency.
I'm Attila Fejér, the founder of Craftosphere. I'm a software engineer, I work with AI every day, and I run a small company myself, so I know what a Friday spent with spreadsheets costs. I'll tell you where AI pays off in your company and where it doesn't. The person who scopes your project is the same person who answers your email.
How it works
Evaluation first, build second.
- 1
Evaluation: which of your work could run itself?
Half a day with the people who do the work, on site or by video.
You get a written evaluation: this stays a spreadsheet and we fix it, this becomes software, this is where AI is justified, this we leave alone. The evaluation has its own fixed price, from €550. The build is priced separately, in writing, once the evaluation exists. You can stop there. Prices exclude VAT.
The evaluation is yours whatever you decide, and any supplier can work from it.
- 2
Build: using the tool that fits your needs
A repaired spreadsheet, a custom system, an AI-assisted workflow.
A price agreed in writing, working results every week on your data, and you approve every change before it costs anything.
- 3
Handover: everything is yours
Everything you need to run and extend the system without us.
Source code, training for your people, the platform accounts in your name, and documentation another engineer can take the system over from.
We build with AI for speed. An engineer decides what to build and what to trust, so you can run a business on it.
What you get
Each one to remove a pain from the list above.
One place for the numbers
Everyone works on the same data, so the two-totals problem goes away.
Rules the system enforces
A price below cost or a missing date is caught on entry, so errors stop there instead of at month-end.
Reports that come out the same every time
The month-end report is a button, so nobody spends Friday rebuilding it.
Who can change what
Each person sees and edits what their role needs, so one stray edit can't take the business down.
Connections where they pay off
Where your accounting or ERP system allows it, data flows in and out without retyping. We check what's possible in the evaluation.
AI only where it earns its place
Reading documents, sorting requests, drafting the routine reply. Never where a rule does the job better, and never without a person able to check AI's output.
Your data, your system
You own the data and the documentation. Where there is source code, it's yours. Excel export is one click, for the things Excel is still good at.
Documentation and training
The people who use it are trained on it. The documentation is written so another engineer could take the system over.
Who this is for
- A small or medium business where a process that matters (pricing, stock, planning, invoicing, reporting, the inbox) runs on spreadsheets, email and copy-paste, and several people depend on it.
- An owner or operations lead who can decide, and one colleague who knows the work and can spend a few hours a week with us.
- Your process already works, but your tools struggle.
Who this isn't for
- You want to automate a process nobody owns and that changes every week. That needs an owner before it needs a system.
- You want a big all-in-one system. We fix the piece that hurts and connect it to the rest. We can recommend systems we have good experience with.
- You want a product to sell to the market. We build tools for running your own business.
- You want to use the system to let people go. We don't build automation to replace people but to free them for the work they're good at.
What you risk: very little
A spreadsheet became a system
An HR department calculated a regulated payment in one spreadsheet that fewer than five people used. What replaced it, why the first version of the system did nothing more than the original spreadsheet, and what HR considered a win.
Read the case studyNothing taken on faith
You get working results every week, on your data. The evaluation is yours as soon as it's delivered. The documentation is yours after handover. At every step you have evidence, not our word.
The engineer behind it
Craftosphere is run by Attila Fejér, who has built software since 2010: from an HR department inside a Fortune 100 company to companies of six people. He also coaches large engineering teams. The standards he teaches them are the same standards we hold our own work to.
A price that can't run away
The price is agreed in writing before we start. Changes are agreed and priced before they happen, and nothing costs anything without your yes.
Questions business owners ask
Businesses: our offer
Yes, where it's the right tool. For businesses whose reporting, pricing, stock, planning, invoicing or inbox runs on spreadsheets, email and copy-paste, we first judge which work is worth fixing and with what, then build at a price agreed in writing, in weeks. See how it works.
Probably less than you have been told. Most repetitive work is based on rules, and rules want a system, not an AI model. AI earns its place where the input is messy: documents, emails, or free text. We'll tell you in the evaluation what your best options are.
The evaluation is half a day for a fixed price from €550, agreed before we start. The build is a price agreed in writing for the written scope. It covers the build, the handover, and the training. We only work on a daily rate in exceptional situations, for companies whose purchasing only allows those.
The evaluation takes half a day with your people and a few days of creating the written recommendations. A typical build takes weeks from the agreed scope to handover. Custom software used to mean months. Building with AI is what makes weeks possible, and testing on your real data is why it's still weeks rather than days.
Businesses: working with us
It will, and our solution assumes it. The rules live in one place inside the system, so a change is only one change, tested once. The settings that change often (prices, thresholds, categories) are built in a way that your people can change them without an engineer. During the build, changes are agreed and priced before they happen. After handover, small changes are possible for a small agreed price.
The ones that work well as spreadsheets stay, fixed where needed. The ones your business has outgrown get replaced by a system built for the job: we import your data, keep the old files as an archive, and you can still export to Excel for analysis.
Often, depending on the system. Accounting and invoicing systems differ in what they let other software read and write. We check yours in the evaluation and tell you before the price is agreed. Where a live connection isn't possible, we build a clean export and import instead of a fragile workaround.
You don't need to be. You know your process, and that's the expertise we need. We talk in your terms, show you working results instead of diagrams, and our best guide is the colleague who does the work today. The only technical decision you make is yes or no to a written scope.
Sometimes it's the right answer, and we say so in the evaluation. No-code tools fit simple forms and lists. They struggle with rules that have exceptions, data from several places, and reports that must be right. We pick the tool that fits, and the logic stays documented so you aren't locked in.
The difference is what the money buys: a system tested against your data, documented, and yours. AI does the typing and one senior engineer does the deciding, which is why a scoped build fits a small business budget. A price that's agreed in writing is worth more than one that starts low then spirals out of control.
Access to the spreadsheets, the inbox or whatever runs the work, the people who do it, a few hours a week from one colleague while we build, and quick answers when we ask. The rest is our job.
Businesses: who owns the results?
Yes. The data, the documentation and the hosting account are yours. Where there is source code, it's yours. Where we use a platform, the account and the configuration are yours. You can hand the system to another engineer at any time, and the documentation is written for exactly that.
- You own everything, and the documentation is written in a way that an engineer who has never met us can pick up the work.
- We build with widely used, standard technology, so any competent engineer can take it over.
In your accounts. We have access during the build and hand the keys back at handover. Nothing about your business leaves your account.
Bring the spreadsheet. Leave with a straight answer.
A short conversation about the work that eats your people's time. You leave with a straight answer on whether it's worth fixing, even if it's "not yet".
No newsletter, no follow-up sequence.