Request a proposal
Tell us what's messy. Get a scoped proposal.
Send us the problem and we'll come back with a written proposal: how we'd approach it, the phases, what's included, and what the investment looks like. No obligation, and nothing you send goes anywhere except to us.
The proposal process
No pressure to fit the problem into a predefined product. We first determine what should actually be built.
01
You describe the problem
In your own words, with as much or as little detail as you have.
02
MessyOrg reviews the request
A real person reads it, the founder, not a queue.
03
Scope and requirements are clarified
Questions, and a short call where it helps.
04
You receive a written proposal
Sent to you in writing, so it can be shared internally.
05
The proposal defines the engagement
Approach, phases, inclusions, exclusions, timeline, ownership considerations and investment.
What happens after you submit
You are starting a conversation, not buying anything. We reply by email, within 24 hours, with questions or a scoped proposal. If it makes sense to go ahead, we agree the scope and terms in writing first, payment only happens after that, and never through this form.
What we scope around
- Workflows: Built around how your organization actually operates.
- Experience: Interfaces designed for your users and brand.
- Business logic: Rules and automation specific to your organization.
- Data: Architecture designed around your information and requirements.
- Integrations: Connections to the systems your company already depends on.
- AI: AI behaviour, context, automation and guardrails designed for your use case.
Every build is different.
Final investment depends on scope, integrations, security requirements, number of users, data complexity, timeline and ongoing support. We scope each engagement before providing a final proposal.
See engagement modelsConsidering an enterprise engagement?
Review our approach to security, ownership, AI, and production software.

