The hardest part of building Upbuild isn't the technology.
It's this:
The people we're building for have been let down by a lot of things that promised to help them.
Platforms that took their fees and left them to figure out the rest.
Accelerators that wanted equity before they'd offer a room.
VCs who said come back when you have more —
and never defined what more meant.
So when we show up and say "we built this for you" —
We understand why the first reaction isn't trust.
It's caution.
And honestly? That caution is completely earned.
The hardest part of building Upbuild is knowing we have to earn what the system has already spent.
We're okay with that.
We're not going anywhere.
We're not closing our DMs.
We're not hiding behind a form.
We're here.
We're building this in public. All of it. — Upbuild
We're not asking you to trust us immediately. We're asking for 20 minutes. No pitch. No form. Just a real conversation about where you are, what you've tried, and what's been in the way, with the people building this.
https://calendly.com/we-upbuild/30min
The problem you're naming is real and specific: when a community has been over-promised and under-delivered by multiple platforms in sequence, the trust debt isn't with you individually — it's structural. Every new entrant inherits it regardless of their intentions.
Building multiple SaaS products, I've seen the same dynamic play out on the B2B side. When you're selling to a buyer who has been burned before by tools that promised ROI and delivered complexity, the first question isn't "does this work?" It's "why would this be different?" And that question doesn't get answered by your pitch — it gets answered by everything else: how you respond when something breaks, whether you're reachable, whether you change your product based on their feedback rather than your roadmap.
The "building in public" approach you're taking addresses this exactly right. Transparency about process is more credible than promises about outcomes, because it's verifiable in real time. People can watch you respond to setbacks, update your thinking, and stay consistent over months.
One thing worth thinking about as you scale the 20-minute call model: those early conversations are doing double duty — they're both building trust AND giving you the raw material to understand what specific failures your users are still carrying from before. The language people use when describing what went wrong with previous platforms is often the exact language you should put on your website. Not a summary of it — the actual words. That's usually the fastest bridge from skepticism to "this feels different."
Strong problem. The “contracts fail because they’re vague” insight is spot on.
I’d focus a lot on trust — people will care more about risk than speed here.
Are you letting users tweak clauses after generation?
The trust deficit you're describing is real and something I think about a lot as a founder. When you're early-stage and asking people to believe in something that doesn't have years of social proof behind it, every interaction carries disproportionate weight. One bad experience with a previous platform poisons the well for everyone who comes after.
What I've found building our own SaaS is that the fastest way to close that trust gap isn't promises or branding — it's letting people experience the value before you ask for anything. We let users generate their first set of ad creatives without even creating an account. That single decision — leading with the output, not the pitch — changed our conversion story completely.
The "building in public" approach you're taking is smart for exactly this reason. It's hard to distrust someone when you can literally watch them build the thing in real time. Curious how the 20-minute conversation model is converting for you — are people booking, and if so, what's the typical concern they bring to the call?