Skip to content
Devlumio

How we work

From a conversation
to something useful.

A clear scope. Decisions made together. Working previews along the way. Here’s what a project with Devlumio looks like.

Start a conversation
Paper mobile app wireframes with a pen and ruler for planning the user experience.

The project, step by step

You’re part
of the process.

Your knowledge of the business shapes the work. These four stages adapt to your website, business tool, or app; the proposal defines the detail and review points.

  1. Discover

    Understand the problem, review the starting point, and define a useful scope.

    • A discussion of the business and the people using the product
    • Review of relevant existing code, content, or workflows
    • Priorities split between the first version and later possibilities
    • A written proposal with fees, assumptions, and dependencies

    What you can expect

    A proposed scope, budget, and milestone plan

  2. Design

    Make the important flows and decisions visible before building them out.

    • Structure and key user journeys suited to the project
    • Wireframes or prototypes where they help answer a question
    • Visual direction and interface patterns for review
    • Accessibility criteria and a plan for validation

    What you can expect

    Agreed designs or technical approach for the scoped work

  3. Develop

    Build in agreed milestones, with work available for review along the way.

    • Milestones matched to the scope and dependencies
    • A suitable preview or test build when the project allows
    • Testing and code review within the agreed coverage
    • Progress updates at the cadence set for the engagement

    What you can expect

    An implementation reviewed against the agreed acceptance criteria

  4. Launch

    Prepare the release and complete the handover defined in the agreement.

    • Deployment checks and release responsibilities agreed in advance
    • Store submission preparation where included in scope
    • Documentation, access, and ownership transfer as agreed
    • Clear boundaries for fixes, maintenance, and any ongoing support

    What you can expect

    The agreed release and handover, with next steps documented

Before work begins

The practical things.
Agreed in writing.

  • Cost and scope

    The proposal sets out the work, fees, payment stages, and exclusions. If a new requirement changes the cost or priorities, we agree on the impact before proceeding.

  • Timing and feedback

    Milestones account for the build, your review time, and dependencies such as content or account access. We agree on where feedback belongs and how often to check in.

  • Ownership and support

    Source files, account access, licences, and handover are addressed in writing. Continued development, maintenance, and response times are scoped separately.

Good questions

Before
we begin.

How much does a project cost?
Pricing depends on the work, the existing product, and the level of support you need. Share a budget range if you have one. Scope, fees, payment stages, and how changes are handled are agreed in a written proposal before work starts.
How long will it take?
A useful schedule starts with a clear scope and an understanding of any existing code, content, or integrations. Milestones and dependencies are set out in the written proposal. If you have a deadline, include it in your first message so feasibility can be discussed.
Who owns the code and the designs?
Ownership, licences, account access, and the timing of any transfer are agreed in writing before work starts. The agreement distinguishes project deliverables from existing tools and third-party software, which may carry their own licences. Handover is part of that scope.
Can you work with an existing product or team?
Yes. An initial review can help identify what is already working, what needs to change, and how Devlumio would fit alongside your team. The extent of that review and any implementation work are agreed before starting.
Do you build games as well as apps?
Game prototypes and development can be discussed alongside app and web projects. The first step is to define a manageable core experience and target platform. Studio experiments are labelled with their current status; a concept is not a released game.
What happens after launch?
Handover, documentation, fixes, and ongoing support are defined in the project agreement. Continued development or maintenance can be scoped separately. Response times, coverage, and any recurring fees need to be agreed; they are not automatically included.
Can we discuss an NDA?
Yes. Mention confidentiality requirements before sending sensitive material. Any NDA needs to be reviewed and agreed before confidential details are shared.
How do we start?
Email a short description of the problem, who it is for, and what you have so far. The contact page can help you prepare that brief. The first exchange is about fit, open questions, and a sensible next step; sending an enquiry does not commit you to a project.

Your next step

Start where you are.

An outline in your own words is enough. Share what you are working on, who it is for, and what you need next.

Discuss your projectExplore services