Less time fighting the tools.
More time on what you're good at.
- Businesses: the spreadsheet everyone depends on, the shared inbox sorted by hand. We take that work off your people, with the right tool.
- Software companies: your engineers ship AI-written code faster than anyone can judge it. We make sure they get sharper, not sloppier.
What does your company do?
We run a business.
We spend half a day with the people who do the work and tell you, in writing, what's worth fixing and with what. Sometimes AI, often not.
See how it worksWe build software.
Engineering judgment as AI writes more of the code: measured in a Scorecard, practiced in the Dojo, applied in a sprint.
See how we work with engineering teamsCraftosphere is a Budapest-based company that works with two kinds of clients. For businesses, it takes repetitive work off people with the tool that fits: a repaired spreadsheet, a custom system, or AI where it's justified. For software companies, it keeps engineering judgment sharp as AI writes more of the code: the Engineering Quality Scorecard assesses it, the Judgment Dojo practices it, and the Precision Sprint applies it to one bounded problem. Every engagement has a price agreed in writing before work starts, results come in weeks, and the client keeps everything we build. Attila Fejér founded Craftosphere. He has built software since 2010 and coached more than 400 engineering teams since 2013.
-
A price agreed before we start
In writing, and it doesn't move unless you change the scope.
-
Weeks, not quarters
You see working results every week.
-
You own the result
Your data, your documentation, your system.
-
A straight answer
If we aren't the right answer, we say so in the first conversation.
You're dealing with a person, not a faceless agency.
I'm Attila Fejér, the founder of Craftosphere. I have built software since 2010, including at a global technology enterprise, and coached engineering teams since 2013, more than 400 of them, from startups to a Fortune 100 financial company.
The largest program I have coached on so far was at that Fortune 100 organization moving its teams from Scrum toward extreme programming. I coached 300+ of those teams. The case study tells what stuck and what didn't. I run a small company myself, so I know what a Friday spent with spreadsheets costs.
The person who scopes your engagement is the same person who answers your email.
- Since 2010
- building software for a living
- Since 2013
- coaching engineering teams
- 400+
- engineering teams coached
How we work
- 1
You get in touch.
A short conversation, in person in Budapest, by phone or by video call. No preparation necessary: bring the spreadsheet or the codebase. You leave with a straight answer for free, even if the answer is that someone else fits better.
- 2
You get a written scope with a price agreed before we start.
What we'll build or measure, what it costs, and how long it takes. Nothing costs anything before you say yes, and the scoping stays yours even if you say no.
- 3
You see the progress every week.
Working results from the first week. You correct us while corrections are cheap. At the end, the system and the documentation are yours.
We build with AI for speed. An engineer decides what to build and what to trust, so you can rely on the result.
Bring the spreadsheet, or bring the codebase.
A short, free conversation. You leave knowing whether it's worth fixing, and whether we're the right partners to fix it.
No newsletter, no follow-up sequence, and no second call, unless you ask for one.