Contact
What do you
have in mind?
A new website, a useful business tool, or an app you want to bring to life. Tell me what you’re working on. We’ll work out a sensible next step.
Direct to Devlumio
Start with
a short email.
mshlalmnswb@gmail.comReplies within 1 business day.
You do not need a finished brief. A few details help me understand the work and whether Devlumio is a good fit.
Useful things to include
The problem
What needs to work better, and who is it for?
The starting point
An idea, an existing product, or a process you want to improve.
The constraints
Your priorities, budget range, and any dates that matter.
If the work is a fit, the next step is to clarify the scope and agree a written proposal. Timing, price, ownership, and support are settled there.
Keep your first message free of passwords or sensitive customer data. If you need an NDA, mention it before sharing confidential details.
A little structure, if it helps
Put your brief together.
Before we talk
A few
practical details.
Scope first. Clear expectations before the work starts.
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.