From first commit to paying users

A SaaS developer who has shipped the whole thing, more than once

Founding engineer of a time-tracking SaaS on eight platforms, principal engineer of an email client that reached the App Store in four months, and owner of a chat product that paid my bills for five years. Billing, tenants, SSO, stores, support. I have done each part and I know which one bites.

Book a free 30-min call Email me instead

Available from November 2026 · Wrocław, Poland (CET), remote

“someone you can always count on”public LinkedIn recommendation
“a true bias for action”client CTO, on LinkedIn
15+ yearsshipping software
Free call, no pitch deck30 minutes, then you decide

4months from first commit to the App Store

8platforms shipped for Sandtime.io as founding engineer

8,000+commits on one product, close to half of all merges

30,000concurrent users on my own chat app

Week one has something to touch

An MVP is a vertical slice with a login, one feature and an event in PostHog, deployed. Everything after that is prioritized by what the slice taught us.

Billing and tenants without drama

Paddle, Stripe, Mac App Store subscriptions, multi-tenant routing, SSO, custom subdomains. The boring parts of SaaS are where products stall, so I do them first and once.

Measured from day one

A tracking plan per feature before the feature is built. Activation, retention and revenue on dashboards leadership reads without asking me.

The founder’s inbox

I ran support for a product with 1.5 million downloads myself. Users tell you what to build next if someone is listening.

Proof

Work I can show

Problem, what I did, result. Client names only where I am allowed to use them.

Patriot Mail: from first commit to the App Store in four months

The problem: A greenfield AI-native email client for web, iOS and macOS had to reach real users fast, pass Google’s CASA Tier 2 security assessment and work for older people.
What I did: I was the principal engineer. I wrote the delivery plan, shaped the product vision and treated prompt injection through untrusted email as a design constraint before any model touched a mailbox. CASA and OWASP ASVS controls became a Playwright suite that runs on every pull request. WCAG 2.2 AA sits behind an automated axe gate.
Result: Public App Store release in four months. CASA Tier 2 passed and the yearly questionnaire turned into a check on every PR. Text scaling to 200% and a calm-email mode shipped for older users.

4 months CASA Tier 2 WCAG 2.2 AA Open ↗

See also: Mobile & desktop apps · AI & agents

Sandtime.io: founding engineer, eight platforms, one codebase

The problem: A time-tracking SaaS had to live where people work: desktop tray, browser, phone and app stores.
What I did: I authored the original product vision and architecture in 2018 and made the first commit. React Native wrappers for iOS and Android, Electron for macOS, Windows and Linux, a Chrome extension, multi-tenant routing, SSO, Dockerized services, Paddle and Mac App Store subscriptions, CI/CD.
Result: Eight platforms shipped and run in production. The only engineer active in every year of the product, 8,000+ commits and close to half of all merges to trunk.

8 platforms 8,000+ commits since 2018 Open ↗

My own chat app: 30,000 concurrent users on sharded .NET servers

The problem: An ad-supported anonymous chat grew faster than one server could carry, and nobody else was going to run it.
What I did: Horizontally scaled, sharded C# and .NET servers, my own chat network, a moderation panel, automated NSFW detection, support answered by me.
Result: 30,000 concurrent users and 1.5 million+ downloads. It paid my bills for five years and ended when Windows Phone did.

30,000 concurrent 1.5M+ downloads 5 years

Not ready for a project? Start smaller.

Two ways to see how I work before you commit to a sprint. Fixed scope, a number in writing after a short call.

SaaS & MVP codebase audit, one week

I read the repo, CI, tests, security and the parts the team avoids. You get a written report with findings ranked by risk, a plan with milestones and a go or no-go you can defend. I have run this for a large software house before its clients saw the code.

Code review of one pull request or one module

Send me the diff that worries you. Within a few days you get line-level comments, the three things I would change first and whether I would merge it.

Ask about an audit Free 30-minute call first. If an audit is the wrong tool, I say so on the call.

Live demo

Plan your first four weeks

Pick a product type and the features you believe you need. The planner lays them into four weeks with something a user can touch in week one, writes a PostHog event plan per feature and a Definition of Done. Export it to Markdown and bring it to our call.

Demo loading…

Notice how many features fall into “after launch”. That is the point.

How it works

Three steps from this page to a running project.

1
A 30-minute call
You describe the product and the problem. I ask the questions I would ask on day one. If I am not the right person, I say so and point you to someone who is.
2
Scope in writing
A short written plan follows: what we build first, what we measure, how we work together and what it costs. No slide deck.
3
Something to touch in week one
The first slice ships in the first week: deployed, measured, reviewable. From there the work is paced by what the numbers say.

Book a free call Email me instead

Fit check

Is this a fit?

A good fit when

You need a senior who owns delivery, not a pair of hands
The product has to ship and be measured, with or without a product manager
A solo engagement or a team of up to four
TypeScript, React, Node.js, Cloudflare, Postgres, PostHog

Probably not when

A program that needs a ten-person vendor team
A stack built around Java, Python or a cloud I do not sell
Body leasing by the hour with no say in how the work is done
A start before November 2026

Working style

How I work

No product manager? Fine.

Where there is no PM I set priorities directly with the people using the software and answer support myself.

Measured, not assumed

PostHog in every project from day one. A tracking plan per feature and dashboards leadership actually reads.

Zero bug policy

A bug is fixed or consciously closed, never parked. Alerts and error tracking in every project, so I learn about problems before the client does.

FAQ

Questions people ask before they book

How long does an MVP take?

Four to eight weeks for something people can pay for, if the scope is honest. An email client with AI features went from first commit to a public App Store release in four months.

Billing: Stripe, Paddle or the app stores?

Stripe for most web products, Paddle when you want the merchant of record to handle tax, app store subscriptions when the product lives in the stores. I have shipped all three and the receipt-matching bugs that come with them. Store specifics are on the mobile and desktop apps page.

Multi-tenant from the start?

Yes, cheaply: a tenant column, scoped queries, a routing rule for subdomains. Retrofitting it later costs ten times more.

What happens after launch?

The dashboards tell us. Activation first, then retention, then revenue. I stay on as the engineer or hand over to your team with docs that match the product.

Can you work without a product manager?

That is my default mode. I set priorities with the people using the software, answer support and bring the numbers to the weekly call.

How soon can you start?

November 2026. Book the call and bring the four-week plan from the demo.

Let’s find out in 30 minutes

A free 30-minute call. You bring the problem, I bring questions. No prices on this page because scope comes first.

If I am the wrong person I will say so on the call and point you to someone better.