Hey everyone, just wanted to share something I realized through the experience of selling Bubble apps. This might sound super basic to some, but I hope it helps some-one. My idea is:
Instead of sending just a list of features, I love building super simple, blurry wireframes, to show the client the why/how/what of the project.
To me, those wireframes feel like seeing the project through the eyes of a very nearsighted person:
No pixel-perfect UI.
No final copy, colors, spacing, or even strict layouts.
Just shapes and flows to illustrate decisions without locking us into aesthetics.
Here’s how I do it:
At this early stage, we should be talking about features, behaviors, and architecture — not about typography or margins.
In my experience, these lofi wireframes create the perfect space for collaboration. Over time, I’ve found that embedding these rough sketches into the proposal itself creates a totally different feeling for the client:
We don’t jump into unnecessary assumptions, nor create misconceptions.
Both parties can “see the what”.
It feels like we’re already building something together — even before the contract is signed.
It shows architecture and priorities visually, which speeds up decision-making.
It’s like the “pull back” moment of a slingshot before a project really takes off.
It builds trust. Clients see how we think, not just what we promise.
Many Bubble developers send a simple list of features when scoping. And that’s absolutely fine.
But if you can pair your feature list with rough, alive, visual suggestions — you’ll notice how much easier it becomes to:
Align expectations.
Structure your database, workflows, and reusables earlier.
Avoid expensive scope changes later.
Would love to hear how you approach scoping.
Have you tried something similar?
Open to trading experiences and learning more.
PS: If you’re an agency owner looking for help with scoping and early stage prototyping on Bubble projects, I’m always happy to connect!
Forget everything you think you need.
Forget what every other dev told you. What’s the #1 problem killing your business today?
Good.
Here’s how this goes:
I’ll solve it in 7 days.
It’ll cost X.
No BS. No delays.
You get a bare-bones, functional app — styled just enough to match your brand.
No design meetings. No endless revisions.
You’ll have it live and working this time next week.
Then we test it in the real world, fix a few rough edges, and you move forward.
Problem solved.
You want to talk about your next problem? Not yet.
We finish this one first. Then we move. Fast.
I can start tomorrow.
This rough pitch wins about 80% of the time — granted, most of my projects come through referrals and YouTube, but the win rate comes down to one thing: Clients appreciate fast iteration.
The reality is, most people have no idea what they actually need until they can touch and use something real.
If a client shows up with a massive Figma file, I still run the same play:
I ask them, “What’s the #1 thing from this Figma you want working first?”
Then I quote them on that — nothing else.
I never quote the whole project.
Here’s why:
They won’t use half of what’s in the Figma — it’s a waste of their money and my time.
The full price would give them sticker shock — and freeze the project before it starts.
They’ve already spent months dreaming about it — but now they expect it built tomorrow.
The second they start using a real version, they’ll change their mind about what’s important.
Quoting smaller chunks builds momentum — fast wins, real results, easy upsells without friction.
