What am I building?

I work as a designer, and I run a design agency. There is not a lot of room in that day for the second layer of work. Sending a quote. Reviewing leads. Matching deliveries. Writing contracts. Then still protecting time for actual design.

The problem is friction. Not any one task. The same blockers, every day. Day-two work that repeats, and eats the hours you needed for the thing you are actually good at.

So the solution was pretty clear. I started building my own stack. Tools that fit how I work, and maybe how other people in tech work too.

SystemOS

SystemOS was first. I built it with my cofounder from our engineering studio. We cared most about one thing: an end-to-end path from lead to closed project. An operating system for the day-to-day of an agency.

Lead onboarding with custom forms and questionnaires. Meeting booking. A management dashboard. Documents: invoices, quotes, contracts, notes. Income tracking and expense tracking. One place, so a project does not get re-typed along the way.

Everything is customizable, and it can run headless. We are also building custom experiences for enterprise customers who need the system to feel like theirs.

We bound AI into the workflows so a lot of it can start from a prompt. Drop in meeting notes, generate a quote, adjust it by hand. Build your invoice templates the same way. For Germany we integrated a proper DATEV export, so the accountant is not the last person still copying from PDFs.

We are heading into private beta in the next weeks. We want to improve it with real studios on it, not just us. More on SystemOS.

Dial

I could never find a time tracker that was not overloaded, and not too complex to actually use. So I built my own.

Dial understands a timeline. It tracks meetings. It sees when you are listening to music, and which programs you are actually in. Next to the projects and tasks you track on purpose.

I did not build it to support hourly billing for freelancers. I noticed, in my own days, that I wanted to understand where a limited amount of time was going. We all have a tight budget of hours. You should be careful with it, and put it on the right things. The hard part is you cannot feel the waste while you are in it. You just get to the evening and the core work is smaller than it should have been.

That is what Dial is for. Tracking by project, so you can see the actual focus.

It has idle detection, auto-tracking, and review cards you validate before anything is yours. You can also track by hand. Connect Slack, Spotify or Apple Music, calendars, so the rest of the day shows up on the timeline too.

It lives in the macOS menu bar. Lightweight. Reports you can actually send.

After using it myself I realized my allocation was off. As a creative you lose time in the details. That can be the work. Sometimes it is just not the focus you thought you had. So you can set time limits and goals on what you track. More on Dial.

PathKit

The third one came from retainer work at Studio Sphere.

Clients want to work with us on product prototypes. Sometimes a bigger project with UI already in Figma. Sometimes just a vision. Both have the same problem: they cannot see how big the thing is, and they cannot really hold their own product in their head.

A new client hires us for ten core screens, to get a sense of the app and move toward an MVP. Most of the time they do not know how big a small app can be. From the beginning, nobody can guess the screen count, or the real size of the project. Right now a lot of people fill that gap by vibe-coding edge cases, without an overview that stays in sync. Even in a worked-out Figma, the prototype and the real app drift, because developers hit more cases once they are in it.

So we built PathKit.

It scans your screens, tries to understand each one, and takes the flows into account. Drag a screen in, copy it from Figma, or send artboards through the PathKit plugin. Auto-sort and auto-wire the flows, or prototype by hand and link them yourself.

Step by step it understands the flow. It can generate edge-case screens and wireframes so you can actually see the product. That is useful for founders and product owners who want to keep control. Small UI decisions make an app clunky and heavy without anyone noticing, because the extra states were never on the page.

PathKit is also a buddy for UX audits. It pushes you toward clarity. What happens if I click the X. Where does that lead.

There is an audit engine with requirements and rules you can rank and adjust. You can let your own agents do the auditing. Plug in a Claude subscription, or use our tokens, for that part of the platform.

Big client projects are heavy in Figma, and heavy on the brain, if every frame is lined up at once. PathKit is sorted by projects and flows. Show a few flows together, or go into the canvas, pick onboarding, review it, jump to the next. We reduced the density so there is room for planning, edge cases, wireframes. Notes and comments with the team. Sketch something out.

This one is my favorite right now. It sits next to Figma, and it also fits into an AI workflow.

That is the point of this moment, I think. Allocate the right work to a model, and the right work to your own mind. Thinking is more important than it has ever been. Understanding your product is not optional for a founder. It shows the gaps, the issues, the risks. It is how you build something that can actually scale, instead of a demo with holes.

We are starting to put PathKit in front of Studio Sphere customers over the next weeks, and we will open a private beta mostly for product design studios. More on PathKit.

Right now

This is what is going on. Building tools that save time and cost, and make the day feel less like a pile of friction.

I would love user feedback, anytime. If you are interested in any of this, or you have a product idea I should put into one of them, feel free to connect.

Thanks for reading.