Skip to content

Studio services

Stop paying agencies €30kfor software nobody wants.

You have an idea, or a platform you have already paid for. You do not need a twenty-page proposal full of billable hours. You need a partner who helps you build the smallest thing that proves people will pay.

What we work with

Production-proven, boring on purpose.

  • Kotlin
  • Spring Boot
  • React
  • TypeScript
  • Astro
  • Odoo
  • PostgreSQL
  • AWS
  • Terraform
  • OpenTofu
  • CI/CD
  • Observability

Engagements

Four stages, in the order most founders meet them.

Start where you are. Each stage ends with something you can act on, not a document you file away.

  • 01 · Validate

    Lean MVP validation & strategy

    We define the smallest possible product to test real demand, map existing infrastructure instead of writing custom code from day one, and set numeric metrics for user intent.

    Best for: Founders with a raw idea who want to avoid spending tens of thousands on unproven software.

    Discuss this stage
  • 02 · Launch

    Prototype execution & analytics

    We build and deploy the lean blueprint: landing pages, low-code workflows and tracking pipelines that return real behaviour from real users, not survey answers.

    Best for: Founders ready to hit the market in weeks rather than months.

    Discuss this stage
  • 03 · Fix

    Code audit & platform optimisation

    Full platform and architecture audit, realistic functional test scenarios and an end-to-end testing matrix that surfaces security gaps and UX friction.

    Best for: Business owners stuck with a disappointing platform or an unresponsive dev agency.

    Discuss this stage
  • 04 · Scale

    Scale-up: Kotlin, React, DevOps

    Once the idea is proven, we move the architecture onto a long-term stack: production-grade Kotlin services, high-performance React frontends and automated CI/CD.

    Best for: Validated products ready for enterprise-grade scalability.

    Discuss this stage

How an engagement runs

No proposal theatre.

Four steps from first call to something running in production.

  1. 1

    Call

    Sixty minutes on your concept, your current stack and the honest constraints.

  2. 2

    Scope

    A written scope with the cost, the timeline and the risks stated plainly.

  3. 3

    Build

    Weekly working software, direct access to both founders, no account managers.

  4. 4

    Hand over

    You own the code, the infrastructure and the documentation. No lock-in.

The difference

Us versus the usual way.

The usual agency

Who you work withA salesperson, then a junior team you never met

What gets builtEverything on the roadmap, billed by the hour

How it is pricedEstimates that move once the invoice is signed

Who owns itA platform you cannot maintain without them

Track recordNo product of their own to be judged by

Working with Lumias

Who you work withTwo founders on your project, start to finish

What gets builtThe smallest build that answers the question

How it is pricedCost, timeline and risk stated before we start

Who owns itYou own the code and the infrastructure

Track recordWe run our own product, so we live with these trade-offs daily

Working with Lumias Studio protected our launch budget. Rita stepped in to review a third-party build, executing over 150 test scenarios to catch critical issues while our warranty was still active.

Inga Rasuma
Founder, I.R. Projects

Before you ask

The questions founders actually ask.

Ask us directly
How much does an MVP cost?

It depends on what has to be proven, which is why the first call is about narrowing that down. What we can promise is a written number before the work starts, and no invoice that moves after it.

Are you really only two people?

Yes. That is a selling point, not a gap: you speak to the people writing the code, and nothing is lost between a salesperson and a junior team. When a project needs more hands, we say so instead of stretching.

Do you take equity instead of fees?

No. We work for a fee, so your equity stays where it belongs and our advice stays honest about whether you should build at all.

What happens to the code afterwards?

You own it. Repositories, infrastructure definitions and documentation are handed over, and we are happy to brief whoever maintains it next.

Can you audit something another agency built?

That is one of the four engagements. We audit the architecture and the code, write realistic test scenarios and run them, so you know what is broken while any warranty is still active.

Let's build the smallest thing that proves people will pay for it.