Custom software, end to end

A full-stack developer who runs the whole project, with or without a team

Scope, architecture, code, tests, deploys, dashboards and the support inbox. Fifteen years of doing all of it, as a solo engineer and as a technical lead of teams of three to four. Where there is no product manager, I set priorities with the people using the software.

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

15+years shipping software

3 to 4engineers in teams I led

~100bids and interviews as the technical counterpart

300+ GBof production data on one platform I led

From scope to production

I write the delivery plan, build the first vertical slice in week one and keep the pipeline green from there. An email client went from first commit to the App Store in four months that way.

Fractional tech lead

A few days a week inside your team: architecture decisions, code review, hiring screens, the estimates for the next quarter. I was the technical counterpart in about a hundred bids and interviews.

Estimates with an AI coefficient

Every line item gets hours and a share that coding agents can absorb. The result is a range, a plan for what the agents do and what the humans do, and a sanity band. The demo below is the same spreadsheet.

Decisions you can trace

Trunk-based development, CI/CD, a stopped initiative when the analysis said it would not pay off. A client CTO called it “a true bias for action” in a public recommendation.

Proof

Work I can show

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

Back-office task management: team lead of four, no product manager

The problem: A back-office tool needed new features, a UI refresh and a faster pipeline, with no product manager in sight.
What I did: I led four engineers and kept coding. Trunk-based development with CI/CD, live updates over server-sent events, a stopped parallel initiative that analysis showed would not pay off, priorities set directly with department managers.
Result: “Measurable changes in some key metrics” and “a true bias for action”, in the client CTO’s public LinkedIn recommendation.

team of 4 CTO recommendation

Suppression-list platform: MVP to product, 300+ GB in production

The problem: A UK email publisher needed suppression lists at terabyte scale with constant-time sign-up and zero-downtime deploys.
What I did: I led three engineers from MVP to the full platform. Postgres partitioning by tenant and list, parallel request pipelines, blue/green deploys. One-click unsubscribe shipped four months before Google and Yahoo required it.
Result: 300+ GB and millions of events in production, zero-downtime deploys, and a compliance feature that landed before the deadline existed.

300+ GB team of 3 blue/green

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: SaaS & MVP · Mobile & desktop apps

One foot in the door

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.

Full-stack & custom software 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

Estimate with an AI coefficient

Add acceptance criteria, give each one hours and a coefficient for how much of it a coding agent can absorb. The totals show human hours, agent-absorbed hours and a sanity band. It saves in your browser only and exports to Markdown for your next planning call.

Demo loading…

Start from the sample project and change the coefficients. A coefficient of 0.9 is not a typo for boilerplate.

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.

Review as a craft

Hundreds of pull requests reviewed. I review for the product and its reasons. The code comes second.

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

What is a fractional tech lead engagement?

Usually two to three days a week for at least three months: architecture, review, hiring, estimates, the hard conversations with stakeholders. Your team keeps shipping, I keep the direction and the quality bar. Details on the offer ladder.

What size of team do you lead?

Three to four engineers works best. I led four on a back-office product, three on a data platform rated 5.0 on Clutch, and integrated ten-plus developers on a micro-frontend MVP.

Which time zones?

I am in Wrocław (CET). I have worked across a nine-hour gap with a US client and daily with UK teams. English is my working language.

Do you start with an audit?

For an existing codebase, yes: one to two weeks, findings you can act on, a plan with milestones. For greenfield, a scoping session and a first slice in week one.

What stack?

TypeScript, React, Node.js, Postgres, Cloudflare, PostHog, Playwright. Earlier a decade of C# and .NET. I will not pretend to know what I do not. The AI and agents page covers how I work with coding agents, and the PostHog page covers measurement.

How soon can you start?

November 2026. Book the call and we agree on the first milestone before I start.

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.