01
Consulting & scoping.
You have a problem and aren’t sure what to build. We interrogate the actual requirement, not the requested feature, and recommend an approach — even if the answer is "don’t build this."
SOFTWARETHAT SHIPS,NOT slides.
01 / PracticeEngineering
Engineering
studio, not
an agency.
Two senior generalists. No PMs in the middle. No decks billed at engineer rates.
02 / StackTypescript,
Typescript,
Postgres, Rust
where it earns it.
Boring tech on purpose, sharp tools when the work calls for it. The repo is yours from commit zero.
03 / Tempo14 days,
04 / Engage14 days,
kickoff to
staging deploy.
Median across the last two dozen engagements. Direct Slack to the engineer in the code. Weekly demo.
Start a project2 slots open · Q3 2026
Same-day response, EU & Korea hours. Fixed price when the scope is clear.
→BACKEND //NestJS·LoopBack·Express·Echo·FastAPI·Flask·Laravel·Symfony·Spring Boot·.NET·VaporWEB //React·Vue·Next.js·Svelte·Inertia·LivewireMOBILE //Swift / iOS·Kotlin / Android·React NativeINFRA //Terraform·Kubernetes·Docker·GitLab CI·AWS·Google Cloud·Azure·Bare metalDATA //RDBMS·Redis·GraphQL·Kafka·RabbitMQ·LLMs
02
Build from scratch.
Greenfield systems. We design the data model, pick the stack, write the code, ship it. Fixed price when the scope is clear; T&M when it isn’t.
03
Takeover & maintenance.
Someone else’s codebase, now yours, now ours. We do the archaeology, stabilize it, and ship incremental improvements instead of pitching a rewrite.
04
Infrastructure & deployment.
Provisioning, pipelines, observability, the boring layer underneath the application. Standalone or bundled with a build — bare metal or any of the three clouds.
05
On-call retainer.
A number to call when something fails. Same-business-day response across EU and Korea hours. Reactive incident response plus proactive patches and monitoring.
06
Equity & partnership.
Occasionally, for the right project, we trade some fees for a stake — in the software, the company, or revenue. An option, not a pitch. Structure depends on what’s being built.
All six, one team
Pick any. Combine any. Enter at any phase.
Most engagements are two or three of these stitched together. A few are just one.
- 01Consulting & scopingFigure out what should actually be built.
- 02Build from scratchGreenfield systems, fixed-price or T&M.
- 03Takeover & maintenanceAdopt the codebase, stabilize, ship forward.
- 04Infrastructure & deploymentThe boring layer underneath. Cloud or bare metal.
- 05On-call retainerA number to call. Same business day across EU and Korea.
- 06Equity & partnershipOptional. Stake in the software, company, or revenue.
Six modes. One team.
Clients enter at whichever point fits the problem — a single consult, a full build, or a phone number to call when prod goes sideways. If it's not on this list, we'll say so and probably tell you who to call.
Six modes. One team.
Clients enter at whichever point fits the problem — a single consult, a full build, or a phone number to call when prod goes sideways. If it's not on this list, we'll say so and probably tell you who to call.
01
Consulting & scoping.
You have a problem and aren’t sure what to build. We interrogate the actual requirement, not the requested feature, and recommend an approach — even if the answer is "don’t build this."
02
Build from scratch.
Greenfield systems. We design the data model, pick the stack, write the code, ship it. Fixed price when the scope is clear; T&M when it isn’t.
03
Takeover & maintenance.
Someone else’s codebase, now yours, now ours. We do the archaeology, stabilize it, and ship incremental improvements instead of pitching a rewrite.
04
Infrastructure & deployment.
Provisioning, pipelines, observability, the boring layer underneath the application. Standalone or bundled with a build — bare metal or any of the three clouds.
05
On-call retainer.
A number to call when something fails. Same-business-day response across EU and Korea hours. Reactive incident response plus proactive patches and monitoring.
06
Equity & partnership.
Occasionally, for the right project, we trade some fees for a stake — in the software, the company, or revenue. An option, not a pitch. Structure depends on what’s being built.
All six, one team
Pick any. Combine any. Enter at any phase.
Most engagements are two or three of these stitched together. A few are just one.
- 01Consulting & scopingFigure out what should actually be built.
- 02Build from scratchGreenfield systems, fixed-price or T&M.
- 03Takeover & maintenanceAdopt the codebase, stabilize, ship forward.
- 04Infrastructure & deploymentThe boring layer underneath. Cloud or bare metal.
- 05On-call retainerA number to call. Same business day across EU and Korea.
- 06Equity & partnershipOptional. Stake in the software, company, or revenue.
0
Account managers
You talk to the engineer.
1d
Response window
Same business day, every time.
2×
Regions covered
EU and Korea working hours.
5+
Modes of engagement
Consult, build, take over, run, hold.
How an engagement actually runs.
Most projects don’t run all four phases. Enter at any one — scope only, take over a half-built system, or stay on for the run. Scroll to step through.
ConsultArchitectBuild / TakeoverShip & Run
01
Consult
Understand the problem.
Calls, a shared doc, a written recommendation. We push back when the asked-for solution isn’t the right one. Sometimes this is the whole engagement — clarity, then we walk away.
Outputs
- Recommendation
- Scoping doc
- Estimate range
Typical
1–2 weeks
Fixed-fee or hourly.
Often the whole job.
02
Architect
Plan on paper first.
Before a single endpoint gets written, you see the schema, the service boundaries, the cloud topology, and the rollout sequence. Disagreements happen here — not three sprints in.
Outputs
- Schema
- Architecture diagram
- Deploy plan
- Risk register
Typical
1–3 weeks
Reviewed with your team.
Signed off before build.
03
Build / Takeover
Code lands in your repo.
Greenfield: small, demoable increments on a cadence that fits the work. Inherited: we map it, stabilise it, then keep moving. You own the code from day one either way.
Outputs
- Merged PRs
- Demo cadence
- Runbook
- Test coverage
Typical
Weeks to months
Fixed-scope or T&M.
Equity optional.
04
Ship & Run
Deploy, then stay or step away.
Hand off cleanly — docs, dashboards, the keys — or roll into a monthly retainer with same-business-day response across EU and Korea. Patches and dependency work continuous in the background.
Outputs
- Deploy pipeline
- Observability
- Runbook
- Optional retainer
Typical
Monthly retainer
EU + Korea coverage.
Same-business-day reply.
How an engagement actually runs.
Most projects don’t run all four phases. Enter at any one — scope only, take over a half-built system, or stay on for the run. Scroll to step through.
ConsultArchitectBuild / TakeoverShip & Run
01Consult
Understand the problem.
Calls, a shared doc, a written recommendation. We push back when the asked-for solution isn’t the right one. Sometimes this is the whole engagement — clarity, then we walk away.
Outputs
- Recommendation
- Scoping doc
- Estimate range
Typical
1–2 weeksFixed-fee or hourly.Often the whole job.
02Architect
Plan on paper first.
Before a single endpoint gets written, you see the schema, the service boundaries, the cloud topology, and the rollout sequence. Disagreements happen here — not three sprints in.
Outputs
- Schema
- Architecture diagram
- Deploy plan
- Risk register
Typical
1–3 weeksReviewed with your team.Signed off before build.
03Build / Takeover
Code lands in your repo.
Greenfield: small, demoable increments on a cadence that fits the work. Inherited: we map it, stabilise it, then keep moving. You own the code from day one either way.
Outputs
- Merged PRs
- Demo cadence
- Runbook
- Test coverage
Typical
Weeks to monthsFixed-scope or T&M.Equity optional.
04Ship & Run
Deploy, then stay or step away.
Hand off cleanly — docs, dashboards, the keys — or roll into a monthly retainer with same-business-day response across EU and Korea. Patches and dependency work continuous in the background.
Outputs
- Deploy pipeline
- Observability
- Runbook
- Optional retainer
Typical
Monthly retainerEU + Korea coverage.Same-business-day reply.
Three shapes. One scoping call.
No published rate card. Pricing is per-engagement, fixed or per-hour, after we understand what you’re trying to do. Occasionally — for the right project — we’ll trade some fees for a stake in the software, the company, or revenue.
Short
Consulting & scoping.
pricingPer houror short fixed-fee
A focused engagement to pressure-test the actual problem and recommend an approach. Often the whole engagement — clarity, then we walk away.
- Calls, a shared doc, a written recommendation
- Architecture sketch when the question warrants it
- Honest "don’t build this" when that’s the answer
- Optional SOW for a follow-on build
Most common
Build & takeover.
pricingPer-projector T&M
Greenfield builds or inherited codebases we pick up and evolve. Fixed price when scope is clear, time & materials when it isn’t — never dressed up as the other.
- Engineer-led from first call to merge
- Code in your repo from week one
- Stack picked for the problem, not the trend
- Rolls into on-call retainer on request
Retainer
Run & on-call.
pricingMonthlyretainer
A number to call when prod goes sideways, plus the quiet work that keeps it from going sideways. Infra management, patching, monitoring, incident response.
- Same-business-day response, EU & Korea hours
- Reactive incident work + proactive maintenance
- Bare metal or AWS / Google Cloud / Azure
- Same engineer through the whole engagement
Six things we believe, written down.
If any of these read as obvious, good — they should. They are also the things we got burned for not believing earlier.
01
Ship weekly or admit you’re stuck.
A Friday with nothing merged is not a milestone, it’s a signal. We’d rather raise the flag on Tuesday than on demo day.
02
We pick up the phone when prod breaks.
Same business day, EU or Korea hours. The engineer who built it triages it. No ticketing queue, no L1 → L2 → L3 ladder.
03
Boring stacks, on purpose.
Postgres before the new graph database. Rendered HTML before the next framework. Boring tech is what you can hire for in 2031.
04
You own the code from day one.
Repo, infra, secrets — all in your name from the first commit. No hostage scenarios when you outgrow us.
05
Fixed price when we can, hourly when we must.
If the scope is clear, we’ll quote it flat. If it isn’t, we’ll say so out loud instead of dressing T&M up as something it isn’t.
06
Say no, in writing.
We turn down ~60% of inbound. Wrong problem, wrong stage, wrong fit. A clean no on Tuesday saves everyone six weeks.
Tell us what’s
on the drawing board.
New product, internal tool, or a half-written spec. Send what you have — a problem, a sketch, a one-pager — an engineer reads it and replies same business day.
↦ Routed direct to an engineer
[email protected]