Proper Engineer Send us what you have
Sheet 1 Intakeproperengineer.comRev every version

You vibe‑code the prototype. We build the real product. No team to hire or manage.

Send what you have: a prototype link, a repo, a mockup, a few lines. One engineer builds it properly. A version comes back every week.

  • A tagged version, a demo, a changelog, every week.
  • A plan for week one within two days.
  • Scoped one week at a time.

Keep prototyping with Lovable, Codex, or Cursor. We work in your GitHub and answer in your Slack.

IntakeTwo questions. The plan rewrites itself.

1What do you have?

2What do you want back?

What we do
What we need
Week one

Goes straight to Mike. A plan for week one comes back within two days.

Three things we build

The whole app

Rebuilt to run properly, for many customers.

The next feature

You vibe-code it, we build it in.

The first version

From mockups or an idea.

The prototype works. It can't take real users yet.

Built one feature at a time, each wired straight to whatever it needed.

1234 your team users Database Outside service Sign-in provider Sign-up Dashboard Export customer = "Acme GmbH" password = "hunter2" runs here and nowhere else 1 2 3 4
Sheet 2
As built, marked up in week one
Rev 0
  1. 1Nothing holds the features together. Every change breaks something else.
  2. 2One customer, and their passwords, written into the code.
  3. 3Outside services wired straight in. One changes, the app breaks.
  4. 4Runs on one laptop and nowhere else.

We give it a core every feature runs through, and tests on every change.

“We ask Codex to build another feature and it just does it, out of the box. Nothing else breaks. That’s how we knew the architecture was right.”
Client, KIMA · real-estate deal management, Germany · after ten weeks

Done means real users can sign up, and it holds

Every version is held to a written standard, not a vibe.

1234 Your repo Checks on every change Test copy Live on your own cloud Feature Feature Feature Next feature Core one piece every feature runs through sign-in and roles at the door Customer A Customer B Customer C data kept apart Database Outside service Outside service one contained piece each Secrets,out of the code Backupsand logs Monitoring Security standard Handover notes 1 2 3 4 5 6
Sheet 3
As designed, held to the standard
Rev each version
  1. 1Your own cloud: a test copy, then live. Checks on every change.
  2. 2Sign-in, roles, each customer's data kept apart.
  3. 3One core, one contained piece per outside service.
  4. 4Secrets out of the code. Backups, logs, monitoring on.
  5. 5A written security standard, checked against it.
  6. 6Handover notes for your next engineer.

The acceptance test: real users sign up, use it, and nothing falls over.

Add CSV exportyou sent the prototype, we built it in
Open
export/ + csv.ts writes a report as a file+ csv.test.ts checks the columns and the totals
Tests on the paths that matterwaiting
Security standardwaiting
Deploy to the test copywaiting
Deploy to livewaiting
Nothing has run yet.

Here you send, and a version comes back. Every week.

Vibe coding got you out of hiring, briefing, and managing people. A development team puts that back. It works the way your AI tool does: you send what you have, one engineer builds it. Your feedback on the demo sets the next week. One Slack channel, no standups.

The first weeks of a rebuildUnderstand, rebuild the core, secure it, go live
wk 12345678 UnderstandRebuild the coreSecurity weekGo live what it was meant to do, the mistake underneath, first clean deploythe core, then what the prototype fakedwritten standard, the app checked against ittests, monitoring, handover: live for real users
How long things tookFrom the projects below
Full rebuild, many customers on one appFirst working version, from a mockupScoped plan for week one 10 weeks4 weeks2 days
One week, start to finishIllustrative
You send We build You get a prototype, a feature,or notes on the demo one engineer,checks on every change a tagged version,a demo, a changelog your feedback sets the next week Mondayend of the week

Who came to us, and what they left with

A German real-estate app

Arrived
Separate features, one customer hardcoded in, working half the time.
Left
One core, room for many customers.
Built withCodex
WorkFull rebuild
Time10 weeks

An AI assistant, from a mockup

Arrived
Screens and a wish list, no code.
Left
A working version in four weeks.
Built fromA mockup
WorkFirst version
Time4 weeks

A research team's pipeline, 15 scientists

Arrived
A day or two per run, on one laptop.
Left
A shared cloud pipeline the whole company uses.
Built fromOne laptop
WorkPipeline
TimeOngoing

What it costs

One engineer, priced by the week. Nothing to hire.

Build weeks

A fixed price per week, scoped every Monday.

€4,900a week

Slack desk

Questions and small requests, by the day.

€1,200a day

Maintenance

Once live: monitoring, updates, patches, a monthly check on the core.

7%of build hours, monthly

What you have to do

Send what you have, or twenty minutes on a call. Then one demo a week, and your feedback on it.

If you stop

We scope one week at a time. Everything built is already in your GitHub, with handover notes. Once live, it's your company's software, and the contract says so.

Who you'll be talking to

Mike reads your prototype, answers in your Slack, and signs off every version that ships.

Mike Bjørn
Mike BjørnThe button sends your two answers to him.

The plan for week one comes back within two days.

Two questions at the top of this page.

Send us what you have