Lab pricing
Pay for the project, not a retainer
Every engagement is scoped and quoted as a fixed-fee project. You see the number, the deliverables, and the timeline before we build anything.
Three things set the fee.
The quote comes out of the scoping work itself, so it reflects your project, not a rate card.
Scope
What gets built
A single workflow is a different project from an end-to-end pipeline. The opportunity map narrows it to the highest-value build, and the proposal prices exactly that.
Stack
What it runs on
We build on the tools you already use: Slack, Notion, HubSpot, Airtable, Google Workspace, your own APIs. A stack we can plug into cleanly scopes smaller than one that needs workarounds.
Integrations
How many systems talk
Every connection between systems is real work: auth, error handling, testing against your live data. More integrations mean a bigger scope, and the proposal names each one.
One fixed fee covers all of it.
The proposal is specific enough to hold us to. You know what is in scope before anything starts.
- 01An opportunity map of the highest-value automations in your stack
- 02A scoped, fixed-fee proposal with named deliverables
- 03A two-week build sprint with regular check-ins
- 04A documented handoff your team owns and can extend without us
- 05No retainer and no lock-in: when it is done, you stop paying
From map to fixed fee
The scoping is useful on its own. Even if you never hire us, you leave with a map of where automation pays off in your stack.
- 01
Generate your opportunity map
Start at lab.melwyn.ai/map. A few minutes of context about your role, industry, and team produces a map of where automation creates real leverage. Prefer to talk it through first? Book a discovery call instead.
Generate your map - 02
Review the scoped proposal
We turn the map into a proposal: what gets built, what stack it runs on, what it replaces, and the fixed project fee. You approve the scope before the sprint starts.
What the alternatives cost
The usual routes to a working automation: hire an engineer, which is a year-round salary for what is often a two-week problem, or bring in a big consultancy and pay for months of discovery before anything ships. Lab is scoped to one project, built in a two-week sprint, and handed off documented. When it is done, you stop paying.
How is a melwyn Lab engagement priced?
melwyn Lab engagements are scoped per project. The engagement starts with an opportunity map to identify the highest-value automation in your stack, followed by a scoped proposal with fixed deliverables and a project fee. Pricing is driven by scope, not a monthly retainer.
Why is there no price list on this page?
Because no two projects are the same size. A single Slack digest and a multi-system pipeline are different builds. The proposal prices your specific scope, and you see the fee before anything starts.
What does a melwyn Lab engagement include?
Every Lab engagement includes: an AI-generated opportunity map, a scoped proposal with specific deliverables, a two-week build sprint, regular progress check-ins, and a final handoff with documentation so your team can own what was built.
How long does a melwyn Lab engagement take?
The core build sprint is two weeks. The scoping phase (opportunity map to approved proposal) typically takes one additional week. Total engagement from first contact to handoff is usually three to four weeks.
Is there a retainer or ongoing fee?
No. You pay one fixed project fee, and the engagement ends with a documented handoff your team owns. If a next project comes up, we scope it as a new one. We would rather you outgrow us than depend on us.
Do I need a technical team to work with melwyn Lab?
No. melwyn Lab handles the build. You need a point of contact who understands the workflow being automated and can provide access to the relevant tools. We handle the technical implementation and hand off documentation your team can maintain.
Get your scope
Book a discovery call, or start with the opportunity map and let it do the first pass.