01 AI apps and MVPs

A working product, not a pitch deck

Real web apps with accounts, a database, payments, and the AI features that are the reason the product exists. Then we launch them to real users.

02 How we build

The hard part is what to leave out

Scoping is where we spend the most thought, because a product that launches in weeks and teaches you something beats a complete one that never ships.

AI features are built for the times the model is wrong. Output is checked, uncertain results are flagged instead of passed off as fact, and nothing depends on the model being right every time.

What you get: a live app on your own domain, the source code, the accounts it runs on, and a plain-English guide to how it fits together. If you stay on a monthly plan, we host it for you, and you can take it all with you any time.

03 Sizes of build

Three sizes of first version

Whatever the size, you get one fixed price, written in your proposal after the discovery call, before any work starts.

  • Lean MVP
    4 to 6 weeks

    One core flow and one type of user. Accounts, one AI feature, and launch-ready: analytics, and a starter privacy policy and terms for you to review.

  • Standard MVP
    6 to 10 weeks

    Two or three core flows, payments, an admin view, and more than one AI feature with checks and fallbacks.

  • AI-native product
    10 to 14 weeks

    AI is the product: multi-step agents or search over your own data, quality checks, cost controls, several roles and integrations.

04 After launch

Keep it running, or keep it growing

The same optional monthly plans as our tools. Month to month, cancel with 30 days' notice.

  • Care

    It keeps working

    Time on your projectOnce a monthA monthly check-up, plus fixes when something breaks
    • Hosting and uptime monitoring
    • Security and software updates
    • Reply by the next business day
    • Bugs fixed, no invoice
    • AI usage included
  • RecommendedImprove

    It gets better every month

    Time on your projectEvery other weekA planning session and a working session each month
    • Everything in Care
    • We review how it's used and propose changes
    • You approve, we ship, you get a one-page "what changed" log
    • A new release every month
    • More AI usage included
  • Grow

    It keeps growing

    Time on your projectEvery weekYour project is on our weekly build schedule
    • Everything in Improve
    • New features as you need them
    • A monthly call
    • A release every Friday
    • The most AI usage included
Changes after we agree on scope are estimated and approved by you in writing first.
Your data stays yours. When you leave, you get a full export and your settings.
Paid by invoice. Sent through Stripe, paid by bank transfer (ACH).
The Kampos logo

05 Case study

Kampos

An AI study companion for college students, designed and built by Atlas as its own product, from the first sketch to a public beta.

What we did
Product, design, AI, build
Status
In beta
Audience
College students
Stack
React, serverless, LLMs

06 Questions

Straight answers

Who owns the code?

You do, once it's paid for in full: the source code, the accounts it runs on, and a guide to how it fits together.

What if the AI gets something wrong?

We design for it. Output is checked, uncertain results are flagged instead of passed off as fact, and nothing depends on the model being right every time.

Can you build something bigger?

Yes, in phases. We'd rather launch a first version, learn from real users and price the next phase than quote one big number up front.

Have a product in your head?

Book a free 30-minute call. We'll help you find the smallest version worth launching, and tell you honestly if it should be built yet.

Book a call