MessyOrg

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.

Engagement promise

Clear scope.
Clear ownership.
Clear handoff.

Every MessyOrg engagement defines what we're building, how success will be evaluated, what systems are involved, who owns what, and what happens after launch.

Clear scope

Know what is being built and what isn't.

Visible delivery

Understand where the engagement stands.

Verified software

Understand what was tested and how the application works.

Planned handoff

Know what happens when the build becomes an operating system.

Ongoing support

Know where to go when something changes after launch.

Measurable outcomes

Know what success looks like and whether the solution delivers it.

What happens after you submit

You are starting a conversation, not buying anything. We reply by email, usually within two business days, 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.

Your project

Fields marked * are required. Everything else helps us scope it faster.

The problem, who it affects and what happens today.

Optional.

Optional. Timeline, users, must-haves.

Optional.

We use what you send only to reply to you. Nothing is shared with anyone else.

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 models

Considering an enterprise engagement?

Review our approach to security, ownership, AI, and production software.

Visit the Trust Center

After the proposal

How we work

If you go ahead, this is the path the work follows — and you get a private workspace tracking exactly which stage it's in.

  1. Discover

    We identify workflows, bottlenecks, manual processes, and opportunities where custom software can create measurable value.

  2. Design

    We define the application, user experience, architecture, integrations, security requirements, and success criteria.

  3. Build

    We rapidly build the application using Lovable and the appropriate supporting technology stack.

  4. Verify

    We test what was built, document how it works, identify issues, and validate readiness.

  5. Launch

    We handle integrations, authentication, permissions, production readiness, deployment, and handoff.

  6. Enable

    We provide documentation, training, and guidance so teams understand and confidently use what was built.

  7. Support

    We can remain involved after launch for optimization, enhancements, troubleshooting, and continued development.