Skip to content
Devlumio

How we work

From first call to launched product

Four steps, each with a deliverable you can hold us to. No mystery phases, no invoice you did not see coming.

Start with a call
  1. 01

    Discover

    We map your goals, users, and scope, then agree on a clear plan and budget.

    • A working session to understand the business, not only the feature list
    • User and competitor review, so we are not designing in a vacuum
    • Scope split into must-have, should-have, and later
    • A written estimate with the assumptions it depends on

    You get: A scope document, timeline, and fixed estimate

  2. 02

    Design

    Wireframes become polished, clickable designs you approve before any code.

    • Structure and flow first, in low fidelity, where changes are cheap
    • Visual design applied once the flow is agreed
    • A clickable prototype you can hand to a real user
    • Accessibility checked as part of design, not after

    You get: An approved, clickable prototype and design system

  3. 03

    Develop

    We build in short milestones with working previews you can test along the way.

    • Two-week milestones, each ending in something you can open
    • A preview environment updated on every change
    • Automated tests and code review on the parts that matter
    • A weekly written update — progress, blockers, next

    You get: A tested build on a preview URL, updated continuously

  4. 04

    Launch

    We ship to production, hand over the keys, and support what comes next.

    • Production deployment, monitoring, and backups configured
    • Store submission handled where it applies
    • Repository, accounts, and documentation transferred to you
    • A support plan agreed before we finish, not after

    You get: A live product, full ownership, and a support plan

Working together

What you can expect throughout

These hold from the first milestone to the final handover.

  • Two-week milestones

    Each one ends in something you can open and use — not a status update.

  • A written weekly update

    Progress, blockers, and what is next. Same format, same day, every week.

  • A preview URL from week one

    You watch the product take shape instead of waiting for a reveal.

  • One point of contact

    A person who knows your project, not a rotating support queue.

  • Change priced before it is built

    New scope gets a number and a date before anyone starts on it.

  • Your repository from day one

    Code lands in an account you own. You can read every commit as it happens.

Questions

The things people ask before starting

How much does a project cost?
It depends on scope, but we give you a fixed number before you commit. A marketing website typically starts in the low five figures; a mobile app MVP is usually a multiple of that. After a short discovery call we send a written estimate with the assumptions it rests on, so you can see exactly what would change it.
How long will it take?
A website is usually four to eight weeks. A first app or software release is typically eight to twenty weeks depending on scope. A game takes about six weeks to reach a playable prototype and four to nine months to launch. We commit to milestone dates rather than a single distant deadline.
Who owns the code and the designs?
You do — completely, from the first commit. The repository, design files, domains, and third-party accounts are transferred to you at launch. We do not retain rights to your product and we do not lock you into hosting with us.
Can you work with our existing team or codebase?
Yes. We regularly join an existing codebase, extend an in-house team, or take over a project that stalled. The first step is a short technical review so we can tell you honestly what is worth keeping and what is not.
Do you build games as well as apps?
Yes. We build mobile, web, and indie games, and we publish our own titles too. Game work is milestone-based and starts with a playable prototype of the core loop, because that is the only reliable way to find out whether an idea is fun.
What happens after launch?
You choose. Some clients take the handover and run it themselves — that is a supported outcome, not a failure. Others keep us on a monthly plan for monitoring, patches, and continued development. Either way, launch includes documentation and a walkthrough.
Do you sign NDAs?
Yes, before any detailed discussion if you would like. Send yours over or ask us for a standard mutual NDA.
How do we start?
Send us a short description of what you want to build through the contact form. We reply within one business day with either questions or a suggested call. There is no charge for the first conversation or the estimate that follows.

Ready to run this on your project?

Send a short brief and we’ll come back with the first step: what discovery would cover, and what it costs.

Start a ProjectSee our services