Skip to content

plan two · own

I own the technology behind your app. $2,500 a month.

For founders whose business already runs on a live app. Releases, security, hosting, data and fixes become my problem, and one improvement is always in progress. You make the business decisions. I make the technical ones and carry them.

included every month

What stops being your problem.

  • Every release checked and shipped by me. Nothing reaches your customers untested.
  • Security, logins, permissions and backups kept current, and a tested way back if something breaks.
  • Hosting, domains, email and the vendors behind the app managed, renewed and paid attention to.
  • Bugs fixed as they come up, during business hours, with a two-business-day answer on anything.
  • One improvement in progress at a time: a feature, an integration or a change you asked for.
  • A plain-language note every month: what changed, what is exposed, what is next. No jargon.

not included

So the price stays the price.

  • Building or finishing the app. If it is not live yet, Build comes first.
  • Unlimited requests or a feature backlog worked in parallel. One improvement at a time.
  • Emergency on-call, nights, weekends or same-hour response.
  • A rewrite or a migration disguised as monthly work. Those get their own scope.

named production case

I have done this before. AiudApp is the proof.

Andres came to me for one customer-tracking app. I replaced Tookan dispatch and the Bubble dashboards with Next.js apps, redesigned the Flutter field app, swapped paid Google routing for a self-hosted server and kept Xano as the backend. Then I became a partner in the business.

Read the AiudApp case
production scale
≈60k tasks / month
The connected AiudApp ecosystem currently handles approximately 60,000 tasks per month and is growing.
field-app efficiency
−57.5% requests / user-hour
Observed backend requests per active user-hour fell from 192.3 to 81.8 after the Flutter flows were improved.
the engagement
6-month migration → ongoing
The Tookan replacement took six months. Work continued for more than a year afterward and remains ongoing.

how a month runs

One improvement forward, everything live kept safe.

  1. Pick the month's improvement

    You tell me what the business needs next. I tell you what it takes and start it. One thing at a time, finished before the next.

  2. Keep everything that is live safe

    Releases reviewed, dependencies updated, backups tested, access checked, costs watched. The boring work that stops the 3 a.m. call.

  3. Fix what breaks, before you hear about it

    Monitoring tells me first. You hear about it when it is handled, with what happened and what changed so it does not happen again.

  4. Tell you where you stand

    One note a month in plain language. You always know what the technology is doing and what it will cost next.

good fit

A real business, on a live app, with nobody senior owning it.

  • A live app that customers, payments or daily operations depend on.
  • Built by an agency, a freelancer who left, AI tools, or by me in Build.
  • A founder who wants the technical side owned, not managed by them.
  • A business comfortable with asynchronous work and a two-business-day answer.

not live yet?

Then the app gets built first. Build is $4,000 fixed and takes about four weeks; Own starts the month it goes live. Most founders do both, and that is the cleanest path.

See plan one, Build

the small print

What the price does and does not include.

$2,500 a month in US dollars, excluding VAT where it applies, billed monthly in advance with a three-month initial term and monthly after that. Hosting, domains and vendors are billed to you by those vendors. Anything outside the list above is quoted before it starts. You can stop at the end of any month after the first three, and everything stays in your name.

apply

Tell me what your business runs on.

A short application, not a technical audit. Do not share credentials, customer data or private source code here. If you would rather talk first, book the 30-minute call.

How you want to be addressed

Where the application decision goes

Company name or product website

A public URL is enough. Do not share access here.

Closest match. Mixed stacks are expected.

Who currently changes the product?

The technical condition that needs ownership now.

This helps protect both calendars from a bad fit.

The next available start is confirmed after the fit check.

One sentence is enough. No project brief or credentials required.

Own starts when the app is live. If it is not, Build comes first.

One application, one reply from Lucian, no CRM or sales sequence.