A first version
people can pay for.

Auth, subscriptions, the one feature your product is actually about, and a real deployment with your name on every account. Built by a studio that runs its own products, prepaid in Hour Blocks of 6, 12 or 24 hours - so you can stop after any block and still own everything built so far.

Auth & accounts Stripe subscriptions One core feature Deployed for real You own everything

Within two business days

Your message goes straight to the studio. No sales queue, no account manager in between.

Prepaid Hour Blocks

Buy 6, 12, or 24 hours up front at $30/hr. Unused hours never expire.

10 live products

10 products of our own, designed, built, deployed and run in-house - the same job you are hiring for.

You own the code

Full source, in your repository, with the reasoning written down. No lock-in to us or anyone else.

The six things
every first version needs.

Not a wish list. This is the minimum that lets a stranger sign up, pay you, get value, and have somewhere to complain - which is the entire definition of a sellable product.

Accounts and access

Signup, login, password reset, email verification, session handling. Boring, and worth doing with the framework built-in rather than inventing: the built-in path has had far more security attention than anything either of us would write. The decision worth thinking about is the tenancy model, because whether an account is a person or an organisation is painful to change later and trivial to decide now.

  • Framework-native auth, not hand-rolled
  • Personal or organisation accounts, decided early
  • Email verification & password reset
  • Optional social or magic-link login
  • Roles kept simple until a team needs more
  • Session and CSRF handling checked

Taking money

The part founders most often postpone and most need first, because an unpaid product teaches you nothing about willingness to pay. Hosted checkout and a hosted customer portal do most of the work, which saves hours you would otherwise spend rebuilding card forms and invoice screens. What we build is the part that is genuinely yours: the webhook handling that decides who has access, and the entitlement check that gates the feature.

  • Hosted checkout & customer portal
  • Plans, trials and upgrade paths
  • Webhook-driven subscription state
  • One entitlement check, used everywhere
  • Failed payment and cancellation handling
  • Tax fields and invoices where required

The feature the product is about

Everything above is scaffolding that every SaaS shares. This is the part that is yours, and it should get the majority of the hours. Our job in the first conversation is to help you find the smallest version of it that still delivers the promise - usually by cutting configurability, cutting the second user type, and doing manually what would otherwise need a month of automation.

  • The smallest honest version of the promise
  • Data model that will not fight you later
  • Manual operations where automation is premature
  • A path built for the customer, not the demo
  • Tests around the flow that earns money
  • Room to extend without a rewrite

Email that arrives

A SaaS that cannot reliably deliver a password reset email is broken in a way users never report - they just leave. Transactional email is set up properly with sender authentication configured so your messages are not silently filed as spam, templates that render in the clients people actually use, and a bounce path so a dead address does not quietly poison your sending reputation. We run our own mail infrastructure on one of our products, so this is a familiar rather than theoretical area.

  • Transactional email through a real provider
  • SPF, DKIM and DMARC configured
  • Templates that render outside one client
  • Bounce and complaint handling
  • Onboarding and lifecycle messages
  • Deliverability checked before launch

Actually live

The MVP is not finished when it works locally. It is finished when it is on a domain, behind TLS, restarting by itself, backing itself up, and telling you when it throws an error. All of this is cheap now and miserable to retrofit once you have customers, so it is part of the build rather than a later phase.

  • A real server, domain and TLS
  • Process supervision and restart on boot
  • Backups with a restore tested once
  • Error monitoring and log retention
  • A staging copy for the next change
  • A deploy your next developer can run

The scope conversation,
in advance.

Every hour spent on something below is an hour not spent finding out whether anyone wants the product. These get cut by default, and we will argue for cutting them if you ask for them.

A custom admin

The framework admin is free, already secure, and nobody outside your company will ever see it. A bespoke back office before your tenth customer is pure cost.

Granular team permissions

Role matrices are expensive to build and to test. Until a real customer has a team with a real conflict, one role per account is enough.

A mobile app

A responsive web application reaches every device today. A native app doubles the surface area and the release process for a first version nobody has validated.

A public API

An API is a promise you have to keep. Make it when a customer asks and is willing to pay, not because it sounds like a platform.

Scale architecture

Queues where they earn their keep, yes. Microservices, sharding and multi-region for a product with zero users is the most expensive way to feel prepared.

What never gets cut

Migrations, tests on the money path, backups with a tested restore, error monitoring, and you owning every account. Small is fine; fragile is not.

We have done this
for ourselves, repeatedly.

The strongest evidence we can offer a founder is that we ship and run our own. 10 products, designed, built, deployed and run in-house, which is exactly the job you are hiring for.

Subscriptions

LearnCoachAssist

A spaced-repetition learning platform with AI-assisted content generation and Stripe subscriptions on Laravel 12. Auth, billing and a core feature - the exact shape of a first sellable version.

Read the case study
Lean infra

SlashKeys

Laravel 13 on SQLite with self-hosted mail through Postfix and OpenDKIM. Proof that the unglamorous launch work - server, deliverability, deployment - is something we do rather than subcontract.

Read the case study
Two-sided

UslugeHR

A booking marketplace with two user types and payments in the middle. A good example of the kind of scope that genuinely needs more than one Hour Block, priced honestly rather than optimistically.

Read the case study

The full set - document signing, price comparison, news aggregation, travel tools, stock education, an AI coaching feature - is on the products page, each with what it runs on and what was hard about it.

Sounds like your project? Prepaid Hour Blocks · reply within two business days
Start a project

Four steps, no discovery call
you have to sit through.

The first conversation is about cutting scope, not selling you more of it. That is where a founder budget is actually saved.

1

Tell us the problem

A few sentences on what you have and what you need. Rough is fine - we ask the questions that matter and tell you honestly if it is not a fit.

2

Pick an Hour Block

Prepay a block of hours - 6, 12, or 24. The block is the budget: we work until it is used, or you top up.

3

Work in the open

Auth and billing first so the money path exists early, then the core feature in slices you can click through and react to while there is still budget to change it.

4

Handover and support

Live on your domain, on your accounts, with the runbook and a short support window. You revoke our access and nothing breaks.

Bought in
prepaid Hour Blocks.

No volume games and no agency margin on top. You buy the block of hours that fits the size of the job, so you know the number before we start rather than after.

Starter 6 hrs
$180

Typically enough for a focused fix, a small feature, or an integration you are stuck on.

Start with Starter
Pro 24 hrs
$720

Typically enough for a larger build with integrations, auth, or billing wired in.

Start with Pro

Every Hour Block is hours at $30/hr with no discount. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire - roll them into the same project or a later top-up. If the work runs long, you buy another block; nothing is billed without you agreeing to it first.

Frequently asked.

How long does an MVP actually take?

Honestly: our MVP Build package starts at 120 hours and $3,600, spread over some weeks, and a smaller first slice can run as Hour Blocks. Anything promising a full SaaS in six hours is selling you a demo. The useful question is not how fast it can be built but how small the first version can be while still being something a person would pay for, and that is the conversation we want to have in the first reply.

What is an Hour Block, and what if the job takes more or fewer hours?

An Hour Block is a prepaid block of hours: Starter is 6 hours for $180, Standard is 12 hours for $360, Pro is 24 hours for $720. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire and roll into the same project or a top-up. For an MVP that means you can stop after any block and still own everything built up to that point.

We have no technical co-founder. Is that a problem?

No, but it changes what you need from us. You need someone who will tell you when an idea is expensive for a reason you had not considered, translate technical trade-offs into cost and risk, and leave you with something another developer can pick up. That is what we aim to be. We will not take equity in place of payment, and we will not pretend to be a co-founder.

What stack will you use?

Laravel or Django, with server-rendered pages and a light sprinkle of Vue where interactivity earns it, Postgres, and a single boring server. Both are mature, well documented and easy to hire for, which matters more than novelty when you are handing the code to someone else in a year. If you already have a stack preference and it is reasonable, we will use yours.

Do we own the code and the accounts?

Yes, all of it, from the first commit. The repository, the server, the domain, the Stripe account and every third-party service are in your name with you as the owner, and we work as a collaborator. When we finish, you revoke our access and nothing stops working.

What do you deliberately leave out of a first version?

Almost everything that is not the core feature plus taking money. Usually cut: a custom admin when the framework admin is fine, granular team permissions before anyone has a team, a mobile app, a public API, internationalisation, and anything justified by traffic you do not have yet. Those are cheap to add once customers exist and expensive to carry while they do not.

Will it survive if it works?

A first version should be small, not fragile. It gets migrations, tests around the paths that take money, backups that have actually been restored once, and error monitoring, because those are cheap now and painful to retrofit. It will not get an architecture built for a scale you have not reached, since that is the most common way founders spend their runway on nothing.

How do we start?

Send a few sentences through the form on this page: who the customer is, what the product does for them, and what would count as proof it works. You get a reply from us directly, usually within two business days, including an honest opinion if we think the scope is too big for a first version.

Tell us what you are trying to sell.

Who the customer is, what the product does for them, and what would count as proof that it works. A few sentences is plenty - we read every message and reply within two business days with an honest read, including if we think the scope is too big for a first version.

Prefer email?

[email protected]
Please enter your name
Please enter a valid email
Which Hour Block?
Tell us a little about the project
Thanks - we have got it.

Expect a reply from us within two business days.

Hour Blocks from $180reply within two business days Start a project