Your next step 1 / 3

What are you working on?

Two quick choices. No technical brief needed.

The first conversation is free. No commitment to a paid service.

00Product studio · web and mobile

We take over your app and keep it running.

Your developer left, launch is stuck, or your product needs a team. We audit what exists, agree on the work, and stay for releases, support and development.

Dilizy DMS, the vehicle card in the dealer management system
Qovo app, home screen
WAH app, the dealers list

What's under the screen

  1. 01Interface

    Screens, sign-in and roles on the web, iOS and Android.

    App Store Guideline 4.8: offer Google sign-in, and you must also offer an equivalent privacy-focused login. Apple App Review Guidelines

  2. 02API

    Payments, webhooks, push and the jobs behind them.

    Stripe retries an undelivered webhook for up to 3 days in live mode, so the handler has to be idempotent. Stripe docs · Webhooks

  3. 03Database

    Postgres, migrations, and backups that get restored, not just taken.

  4. 04Infra & monitoring

    CI → deploy, Sentry alerts, and someone on call.

    Above a 1.09% user-perceived crash rate, Google Play may reduce an app's visibility. Android Developers · Android vitals

01Work

A product moving again.

Qovo came to us unfinished. We kept its backend, rebuilt the mobile app and now run the backend and store releases.

See the Qovo takeover

Below: products we built, co-built or took over — and still run.

  1. 01Used-car inspection

    Qovo

    Inspection marketplace: buyer and inspector apps · Taken over, frontend rebuilt, run

    • Flutter
    • MobX
    • GoRouter
    • Dio
    • Hive
  2. 02Vehicle import

    WAH app

    iOS and Android app for buyers and dealers · Taken over, rebuilt in Flutter and run

    • Flutter
    • MobX
    • go_router
    • Dio
    • drift
  3. 03Automotive retail

    Dilizy DMS

    Dealer management platform (web) · Built and run together with its founders

    • Laravel
    • PHP
    • Inertia
    • Vue 3
    • TypeScript
  4. 04Vehicle import operations

    WAH AI system

    Internal platform on company data, with approval gates · Built and run

    • Claude
    • Node.js
    • MCP
    • Speech-to-text
    • systemd
  1. 06Automotive retail

    Dilizy mobile app

    iOS and Android app over the dealer platform · Built and run

    A Flutter app over the dealer platform: native sign-in with biometric unlock, push that opens the right screen, store releases from CI.

    • Flutter
    • Dart
    • Riverpod
    • Dio
    • go_router

One product. One team.From handover to what comes next

We take it from here.
And stay for the next chapter.

You do not need to choose a technical service. Tell us where your app is; we agree the right starting point together.

First, a conversation about your product.

Free initial audit in 2–3 working days after agreed access. Delivery sprints from $5,000. Ongoing care from $990/month. Initial repairs scoped separately.
Talk about your app

03Where you are

Where is your product now?

01 result

Not built yet.

Web and mobile, from scope to App Store and Google Play release: sign-in, payments, admin, monitoring. Then we keep running it.

what we do first

  1. scope: screens, roles, payments, store accounts
  2. a fixed-price scope — yours to keep
  3. build in milestones → store release
Custom software

02 result

Built, but stuck.

The developer left, a store rejected it, or an AI tool got it most of the way. We audit what exists and finish it.

what we do first

  1. read the code, the store rejection and the error logs
  2. check db access rules · keys in the client · payment webhooks
  3. written audit: keep, fix or replace — then finish it
App takeover

03 result

Live, and needs looking after.

OS and SDK updates, store policy deadlines, dependency upgrades, failed renewals. Monthly care with someone on call.

what we do first

  1. store policy deadlines and SDK targets
  2. sentry alerts → someone on call
  3. monthly updates + a block of hours
App care

04 result

Live, and it needs AI inside.

Features that call a model inside a workflow you already have, with limits, logs and a person approving what goes out.

what we do first

  1. one workflow: where the model is called
  2. limits, logs, a person approving what goes out
  3. shipped inside the app you already run
AI integrations

04Questions

What founders ask first.

No. Flutter, Laravel, Ruby on Rails, Vue, Stripe and Docker are what we run every day, and each case lists its stack. That is evidence of depth, not a limit: an audit starts from your code as it is.

Only if the audit shows a rewrite costs less than fixing what exists, and then the report says why, with specifics. Usually the right move is to keep the working parts and fix the risky ones.

You do. Repository, cloud, store listings and payment accounts stay in your name. We are added with the access the work needs and removed when you say so.

Yes: 30 minutes, no obligation. The initial audit is free too: a written report in 2–3 working days after we receive the agreed materials and access. You keep it even if you do not continue.

The first 30-minute call and initial audit are free. The audit report takes 2–3 working days after agreed materials and access are received. Delivery sprints start at $5,000; full rebuilds and AI MVP production projects are quoted for the agreed scope. Ongoing care starts at $990/month. Fixes, builds and implementation are paid work, agreed separately before starting.

Yes. Apps made with Lovable, Bolt, Replit, Cursor or FlutterFlow are ordinary code underneath. We check what those tools usually leave open: database access rules, keys in the client and payment webhooks.

We're a small studio based in Alicante, Spain. We work remotely, in English, with founders and companies in the US and Canada.

Next step

A short call about what you have, what blocks it and whether we are a fit. Bring the store rejection or the error you keep seeing, if there is one.

A free 30-minute call to understand your product and agree the next step.