Community Wisdom: How to sell a Wized project?
This post is part of my weekly skills series, where I share technical and business learnings related to Webflow.
I’ve just started getting into Wized.
For those who don’t know, Wized is a tool for building advanced apps on top of Webflow. It allows you to build login-based sites where users can interact with data.
Think marketplaces, learning platforms, CRMs, and travel bookings.
Take a look at their showcase, and you’ll get the idea.
I’m looking to take on more advanced projects.
I’ve already built a learning platform using Memberstack, and this looks like the next logical step (especially in combination with Xano, which I’ll talk about another day).
I was really happy to see the Wized team do a live session on YouTube the other day, explaining their sales process for selling Wized projects to clients.
I watched the hour-long talk and made notes so you can get the main learnings.
It’s filled with useful nuggets covering selling both Wized and Webflow.
3:32 How do you scope a Wized project?
Different from scoping a website - it’s more like app scoping
3-4 weeks of scoping
starts from understanding the product you’re building
wireframing, sketching, building proof-of-concept
do you scope for free?
Bailey: YES - bc they close more deals, the value the client gets is unparalleled
you have to set a budget range on the first call to filter out clients with small budgets
with each step in scoping, the range gets smaller and smaller; check with your client at each step if this still makes sense
with each step, your % chance of closing gets higher
Finsweet: NO - it’s a testament to the stage of the industry; educated clients will pay money to get on your calendar so you can do the discovery for them
this is more true of enterprise customers
24:42 Should you price hourly or by value?
if it’s under a week, go hourly
if it’s more, go value-based
32:58 What should be included in a basic maintenance package?
When you sell Wized, sell maintenance as well
Let the customer know you’re there for them in the future; you’ll support them
Sell blocks of hours - customers can use them however they like (usually, there’s a backlog of things to work on)
35:07 How do you plan the team?
Finsweet prefers small teams
No middle man, devs are in the lead positions
Wized projects are developed in pairs - one is stronger in customer comms and the other is stronger in development
38:24 What are the outcomes of a good discovery phase?
good understanding of the project, the client needs to feel heard, all possibilities of what this app could be, has been heard
this includes: sitemap, detailed list of functions and feature
take it further and build a DB schema, define individual API calls on each page
42:46 What about charging by sprint?
these projects don’t have a finite stopping point
split things into phases - phase one is what’s knowable today; phases two, three, etc, are things we’ll learn while building phase one
it’s a great way to just get started - you can do a one-week sprint to just get started and get to know you
48:23 How do you course correct if the scope changes and starts to look unrealistic?
one word answer: honesty
you have to be good at explaining it to them - clearly communicate how much time this adds to the project
don’t pay for client’s mistakes
Your turn
Have you already built an app with Wized or any other no-code platform? What’s your experience selling it to clients?
👋 Happy Webflowing,
Ondrej