Platform builds for founders

Prototype tools and a real build

That second list is what we build.

What you get

1. 1.Python code in your GitHub from the first commit, yours on payment.
2. 2.Security headers, consent and data deletion designed in, not added later.
3. 3.Payments through Stripe, in your own Stripe account: customers pay on Stripe's own checkout page, so card details never touch your servers; every payment notification from Stripe is checked for its signature before the platform acts on it; customers manage subscriptions in Stripe's customer portal; and billing has its own automated tests.
4. 4.VAT handled at checkout: Stripe Tax calculates the right rate for each customer, business customers enter their VAT number and get reverse charge where it applies, and every payment can become an invoice in your accounting or invoicing system automatically (for Romanian companies, through e-Factura). Which registrations and rates apply stays your accountant's decision; we build the system that applies them.
5. 5.A billing page for your customers: they change their card, download invoices, and upgrade, downgrade or cancel on their own through Stripe's customer portal, with no email to you. Only the account owner can change billing. You can also offer a pause plan instead of cancelling, so a customer who stops for a while keeps their account and data.
6. 6.Tests, logging and failure alerts.
7. 7.Documentation and recorded video walkthroughs.
8. 8.Every account in your company's name.

Built to stay up in production

Every change is tested before it goes live, every failure triggers an alert, and security is part of the build from the first commit: secrets kept out of the code, dependencies checked for known vulnerabilities, and each part given only the access it needs.

Before you launch: six questions

Answer these about your prototype. Every no is something real users will find before you do.

1. 1.Do customers pay on a secure checkout, with card details never touching your servers?
2. 2.Is VAT calculated correctly for each customer, and does every payment produce an invoice?
3. 3.Can customers change their card, download invoices or cancel without writing to you?
4. 4.Is every change tested before it reaches your users?
5. 5.Do you get an alert when something fails, before a customer tells you?
6. 6.Is the code in your own repository, readable by any developer?

If you answered no to any of them, send us the prototype for a free written assessment.

How it works

1. 1. Send your idea or prototype link

   Send your idea or prototype link through the contact form.

2. 2. Free written assessment

   Within two working days: what to build first, in which phases, and a fixed price for each phase.

3. 3. Pay and deliver, phase by phase

   Each phase is paid before it starts and delivered with a written acceptance checklist.

4. 4. Fixes

   Fixes for anything that does not work as agreed after each phase.

5. 5. After launch, your choice

   After launch, your choice: run it yourself, or we host and maintain it for you on a dedicated server, as yearly care. The code stays yours either way.

Price

Fixed price per phase, in writing, after the free assessment. Prices are in USD and exclude VAT.

When we say no

• Equity instead of payment.
• Cofounder or employee roles: we work as a company, invoiced.
• Work without a written scope.

Work is in writing and asynchronous; meetings are not needed.

Questions