Scoping and estimation
Before a line of code is written: a defined scope, a priced plan, and the risks named up front, so the budget holds when the work starts.
- You get
- Scope document, estimate, and delivery plan
Available for new projects
I take projects from the first estimate to production: scoping, architecture, delivery, and the security review before launch. AI agents handle the typing. I stay accountable for every decision.
What I do
Most projects fail between the people who estimate, the people who build, and the people who check. I close that gap by doing all three.
End to end delivery
Web, mobile, and backend, from architecture to production deploy. One person responsible for the whole system instead of a chain of handoffs.
- You get
- Production system, documentation, and handover
Code audits and security reviews
A structured review of code quality, access control, performance, and vulnerabilities. Every finding is ranked by severity and comes with a fix.
- You get
- Audit report with prioritized fixes
Automation and AI workflows
Repetitive work turned into pipelines: document ingestion, data synchronization, and agent driven delivery that runs inside your stack.
- You get
- Working automation, monitored and documented
Case studies
Most of my client work is delivered through Rocksoft and covered by NDA, so the names stay out. The problems and the outcomes do not.
Fintech platform, Norway
From Day.js to the Temporal API
- What I did
- Led the migration of the platform's date and time handling from Day.js to the Temporal API.
- Outcome
- The whole platform runs nearly 10x faster, server costs went down, and containers got lighter in local and CI environments.
~10xfaster platform
Fintech platform, Norway
Payment documents, processed automatically
- What I did
- Built ingestion automations that read payment data from source documents and write it into the platform.
- Outcome
- Payment data lands in the system as structured records, directly from the source files.
Property audit company, UK
Audit reports generated from auditor input
- What I did
- Automated report creation from the information and attachments an auditor provides.
- Outcome
- Reports are produced automatically, in the form the legal requirements call for.
How I work
Scope
We define what done means. I map requirements, constraints, and risks before anyone commits to a budget.
Price
You get an estimate split into deployable increments, so every stage can be shipped and verified on its own.
Build
I deliver increment by increment. Agents produce the volume, and I review every change against the plan.
Harden
Before launch: a security and quality review, tests on the critical paths, and a handover your team can run with.
- TypeScript
- React
- Next.js
- React Native
- Node.js
- Tailwind CSS
- GraphQL
- PostgreSQL
- Prisma
- Framer Motion
- Electron
- Vitest
On AI
Typing was never the hard part. Knowing what to build, what it costs, and where it breaks still is. That is where I spend my time.
Specs before prompts
An agent is only as good as the plan it executes. I write the plan.
Review is not optional
Every generated change is read, tested, and checked against the scope.
Accountability stays human
Tools do not sign off on production. I do.
Tell me what you are building or what worries you about what is already built. I usually reply within a day.