Request a proposal.
Describe the requirement. You receive a written assessment with an indicative estimate and the risks identified at this stage.
Project brief
What you receive
Read in full by a person.
No preliminary sales call and no automated follow-up sequence.
A written response within one week.
Scope, a proposed engagement shape, an indicative estimate expressed as a range, and the risks identified at this stage.
A discovery sprint, where the scope requires one.
A fixed-fee engagement that produces a written plan, a risk register and a prototype of the primary flow.
Our own product line is public: 14 products in the catalogue, 13 of them live. Browse products
Prefer email? hello@mobilebytesensei.com
Before you send.
Ownership, confidentiality, how an engagement starts and what it costs.
Who owns the code?
You do — source, infrastructure, accounts and signing keys. Repositories live in your organisation from the first commit, not ours, and ownership transfers on final payment for the work.
Anything that pre-existed your project stays ours, licensed to you perpetually and irrevocably as part of your product. You will never need our permission to keep running what we built.
Will you sign our NDA?
Yes, before the first call if you prefer. We will sign yours or provide ours.
How do we start?
With a scoping engagement: two to three weeks at a fixed fee. It concludes with a written plan, an estimate as a range, a risk register and a clickable prototype of the flow that carries the product.
The fee is credited in full against a build engagement that starts within 90 days. That credit is written into the contract.
What does a project cost?
Cost depends on scope, platforms and duration. An indicative range is provided in the written assessment that follows an enquiry, and where a budget is too small to deliver the work to our standard, the assessment says so.
A firm figure follows scoping. Any number quoted before those questions are answered is an estimate without a basis.