The system behind the build
How specs, small execution plans, review loops, tests, and approval gates made a full production-company operating system possible.
Your tools work. I build the system between them.
When leads, jobs, offers, finance, files, and follow-ups live in different tools, the missing links become somebody’s full-time job. I map that work, build one shared operational system around it, and hand it back on your accounts.
from first build to client handoff
migrated into one eight-stage pipeline
brought together in one centralized operating system
You probably do not need more software.You need the work between the software to stop draining your time.
In a fragmented setup, one confirmed job can create six disconnected records.
The schedule, project folder, crew brief, calendar, invoice, and follow-up each have to be created separately and kept aligned.
Project status lives in conversations.
To see what is selling, scheduled, late, profitable, or blocked, somebody has to ask around and assemble the answer by hand.
The tools work. The system does not.
Your accounting, files, email, and specialist software may be fine. The missing piece is one centralized system connecting them.
What clients say
Valtteri NikkanenCEO, Harju Partners Oy
“The most meaningful thing was not any individual feature. Joonatan built a foundation we can continue adapting ourselves, without depending on him.”
Learn more about the process
What were Fraymful's day-to-day operations and systems like before the project?
Quite fragmented. We had different pieces with different service providers and in different workspaces: Google on its own, financial administration on its own, and Notion on its own. Each worked perfectly well by itself, but they did not communicate with one another. There was no single, unified solution for anything.
What was the biggest practical problem or friction you wanted to solve?
We wanted one system that would connect all of them. We wanted to be able to properly track the business, the growth of two brands, planning, and customers from the same place. We were looking for a comprehensive solution, not yet another new tool alongside all the others.
What did Joonatan build or change that was most meaningful to you?
The most meaningful thing was not any individual feature. It was that he built a foundation we can continue adapting ourselves. We are not dependent on his work. We can make it truly our own and continue developing it independently. That means a great deal to us.
What is concretely better now?
We save time in customer management, sales, and sending emails. The biggest thing is that the whole operation stays under control, which alone saves a great deal of time. Decision-making has also become easier because the financial information is in the same place as everything else.
Did you have any doubts or concerns at the beginning?
I wondered how the data and automations across all the different platforms could actually work through a single page. It is such a broad solution that it concerned me at first.
What was it like working with Joonatan?
The communication was strong and the work felt relaxed. He brought innovative ideas and, most importantly for us, understood our industry as well as our specific business concerns. We did not have to explain the basics.
Who would you recommend Joonatan to, and in what kind of situation?
Definitely small businesses. Running a business can be quite unclear at times, and systems keep changing. This brought a great deal of clarity to the way we work. I would say any small to medium-sized company that offers some kind of product or service and uses several different systems. It is worth reaching out to him.
Choose how much of the system you want to own.
The same system can be managed for you, operated together, or transferred fully to your team.
We run it together
Shared operations
Your team owns the daily operation. I stay involved where useful and deliver small development projects as the system changes.
Shared operation with optional supportWhat I offer.
Three levels, from advice to a working system.
1–3 hours
Operations audit
A focused review of where work slows down and what is worth improving.
Learn more
A focused consultation supported by research and analysis. We review how the business runs, what software and AI it already uses, where time is being lost, and which opportunities are worth pursuing. You receive practical suggestions and a clear build or no-build order.
Research, analysis, consultation, and recommendations.
2–3 days
Workflow automation
One repeatable workflow designed, built, tested, and handed over.
Learn more
We automate one bounded workflow from trigger to outcome. Examples include an offer builder that turns pricing inputs into a branded proposal and customer link, or a daily executive report that gathers the latest sales, project, finance, and operational changes into one decision-ready briefing.
One documented automation, built on your infrastructure.
1–2 weeks
Operating System
Core workflows connected through one tailored system your team can own.
Learn more
The business's core workflows are connected through one tailored operating system. AI-assisted build workflows let us iterate quickly while adapting approvals, integrations, documentation, and ownership to the way your team actually works.
Tailored scope and ownership model agreed before the build.
Start at the smallest level that can produce a useful result.
Get in touchBefore you ask
Are you replacing our existing software?
Usually not. The useful systems stay where they belong. I connect them around one shared operational record and rebuild only the part that is genuinely missing.
Is this an AI-agent project?
No. The product is a better way to run the work. I use AI throughout the build and in selected workflows, but it does not get authority where a person should decide.
What happens when you leave?
The system, accounts, code, documentation, and operating commands stay with you. The handoff is successful only when someone inside can understand and extend it.
What happens in the first conversation?
We identify one costly operational bottleneck, the systems and people around it, and whether it is worth mapping properly. If it is not a build problem, I will say so.
Where does our data go?
The system is designed around your existing data sources and accounts. Access is limited by role, write actions are explicit, and sensitive workflows are agreed before implementation. The map identifies anything that needs specialist security or compliance review.
Can one person handle a business-critical system?
The engagement is deliberately narrow and transparent. If the scope needs a larger team, formal support coverage, or specialist security work, I will identify that before the build rather than pretend otherwise.
Project 52: the work behind the offer.
Three recent builds show the progression from one useful workflow to a complete operating system.
The offer that sells
A real pricing engine, modular branded deck, saved offers, and a shareable customer link turned manual proposals into one repeatable workflow.
I built my own trainer
A focused agent combines Strava, recovery data, a real calendar, and domain guardrails to make useful training decisions.
The other half of my work starts with a camera.
Years in video production taught me to notice handoffs, information gaps, deadlines, and the moment a plan meets reality. Filmmaking is a separate craft and part of how I see the systems behind the work.
Explore filmmaking →