u/Secure_Carry8325

invoicing app for tradesmen. 2.5 years on bubble. £11.2K MRR. 230 customers.

latest rebuild quote: £45K. 4 months. react, node, postgresql.

my customers access the app on their phone between jobs. they dont know what bubble is. they dont know what react is.

what a developer would critique: 2.8 second load time. not fluid mobile responsiveness.

what the developer doesnt ask about: 3.1% monthly churn. 47 NPS. 0.8 support tickets per customer per month.

£45K to rebuild what already works. the rebuild would produce a faster app that 230 customers use the same way.

my rule: rebuild when a customer leaves because of the platform. so far: zero.

invoicing and scheduling tool for tradesmen. built the MVP in bubble because i couldnt code and needed to test the idea. that was 2 years ago.

current state: £9.4K MRR. 180 paying customers. the product works. its not fast. its not elegant. but it processes invoices, sends reminders, and manages schedules reliably.

every developer i talk to says the same thing: "you need to rebuild in react/node/whatever. bubble wont scale. its too slow. its technical debt."

maybe. but heres what i know:

rebuilding would take 3-6 months of development time. during which i'd be maintaining 2 versions of the product. the cost in money and attention would be significant.

the current bubble app serves 180 customers without performance complaints. nobody has churned citing speed. nobody has reported a bug related to the bubble infrastructure.

the "technical debt" everybody warns about is theoretical. the customers who pay me monthly dont know or care that the product is built in bubble. they care that it works.

my rule: rebuild when a customer leaves because of the platform, not when a developer frowns at the platform.

not saying bubble is the right long-term infrastructure. but "rebuild properly" is advice optimized for engineering standards, not business outcomes. and right now the business outcome is 180 happy customers on a platform that works.

any other nocode founders still running their MVPs in production past $5K MRR? curious when the platform actually became the constraint vs when people just told you it would.

Was underpricing for 18 months because I was afraid of losing customers. £39/month for a product that saved tradesmen 2-3 hours per week on invoicing and scheduling.

Raised to £47/month in March. Announced with 30 days notice. Clear email: "We're raising prices because we've added X and Y features and need to sustain the development."

Lost 14 customers. About 8% of the base.

Ran the profitability analysis on the 14 who left. Average support tickets per month: 4.2 (vs 1.3 for the overall base). Average feature requests flagged as "urgent": 2.1 per month. Average payment delays: 8 days past due.

The 14 customers who left at £47 were the most expensive to serve at £39. They consumed 3x the support, paid late, and generated the most friction per pound of revenue.

The remaining 92% are paying more and the support burden dropped proportionally. Revenue up 11% net. Support tickets down 22%.

The price wasn't just a revenue lever. It was a filter. The customers who stay at a fair price are the customers who value the product. The ones who leave over £8/month were tolerating the product at a discount. Tolerance is not loyalty.

growth had plateaued at £8.2K MRR. spent 3 months trying to acquire new customers. marketing experiments. cold outreach. referral incentives. net new: 12 customers. net churn: 11. barely moved.

decided to try the opposite. for 60 days, zero effort on new customer acquisition. all effort on making existing customers happier.

called 30 customers. asked what they wished was better. implemented the 5 most common requests. sent personal emails to each customer whose feedback led to a change. launched a small feature (automatic late payment reminders) that 40+ customers had mentioned.

results after 60 days: 4 customers upgraded to a higher plan. 7 churned customers came back after receiving an email about the late payment reminders feature. 14 new customers arrived through referrals from happy existing customers.

mrr went from £8.2K to £9.4K. 14% growth from zero acquisition spend. the growth came entirely from retention improvements and the referrals that happy customers generated.

the acquisition treadmill was consuming resources that could have been spent making the product better for people already paying. the better product created its own acquisition through referrals.

sometimes the best growth strategy is to stop growing and start caring.

added a "weekly summary email" feature 14 months ago because i had extra time during a slow sprint. the email shows: invoices sent that week, payments received, outstanding amounts, and a one-line cash flow snapshot.

nobody requested it. i built it because i thought it would be useful and it took about 3 days.

14 months later i ran a churn survey. asked customers who stayed beyond 12 months: "what's the main reason you continue using the product?"

expected: the invoicing feature. the payment tracking. the client management.

actual top answer (62% of respondents): "the weekly summary email."

the feature i built in 3 days is the feature that retains customers better than the core product i spent 2 years building.

when i dug into why, the answer was consistent: "it's the only thing that tells me how my business is actually doing without me having to log in and check."

the weekly email is not a feature. it's a habit. every monday morning at 7am, they get a snapshot. they glance at it over coffee. they know where they stand. the email is the weekly ritual that connects them to the product without requiring any effort.

the core product requires login, navigation, and intention. the email requires opening an inbox they're already in. the friction difference between those two actions is the difference between a product people use and a product people depend on.

i now treat the weekly email as the product's most important feature. any change to its format gets more testing than changes to the main dashboard. because the dashboard is where people work. the email is where people stay.

if your saas has retention problems, look at whether you have a zero-friction touchpoint that reaches customers without them coming to you. the product they log into is the product they evaluate. the product that comes to them is the product they keep.

good customer. 3 previous jobs. always paid on time. asked if she could split a £4,200 job into 3 monthly payments because she'd had an unexpected expense. i said yes because the relationship was strong and i trusted her.

she paid the first £1,400. never paid the second. never paid the third. £2,800 outstanding.

first month i waited. "she'll catch up." second month i sent a reminder. friendly. no response. third month i sent a firmer email. read receipt confirmed she saw it. no reply.

called her. went to voicemail. left a message. nothing. sent a text. nothing.

the job was complete. the work was done. i had no leverage because i'd already delivered everything before collecting full payment.

considered small claims court. the filing fee, the time, and the emotional cost of pursuing someone i'd worked with 3 times made me decide against it. wrote off £2,800 and moved on.

the painful part: she was the customer i would have pointed to as the reason i don't need formal payment terms. "she always pays. the relationship is enough." the relationship was enough until it wasn't. and the moment it wasn't, i had nothing. now every job over £2,000 requires 50% upfront before work begins. remaining 50% due on completion before final handoff. no exceptions. no installments. no favours.

3 customers have pushed back on the new terms. all 3 eventually accepted. the customers who refuse to pay upfront are telling you something important about how the project will end.

£2,800 for the lesson that trust is not a payment plan.