Our B2B SaaS Journey

There are genuinely useful operational details buried in the episode - notably the GDPR account-deletion architecture, the sidecar app pattern to keep the core codebase clean, and the white paper framing as authority rather than sales collateral - but they account for perhaps 20 minutes of a 59-minute episode heavily padded with a flood story, LinkedIn vanity metrics, episode-title trivia, and a medieval combat anecdote.

“I don't want the Six Sides code base to really know that much about the police games and this bespoke work that we're doing because that then means that our system stays more generalised”

“we can detach an attendee record from like a user record. So, a user is something you control. That's your profile. An attendee is basically just a relationship between this user went to this event.”

The white paper reframed as an education/authority asset rather than a sales tool is a mildly interesting angle, but nothing else breaks new conceptual ground; the LinkedIn advice ('post about yourself, not your product,' 'consistency over time') and the multi-channel lead gen rationalisation are entirely conventional startup wisdom.

“you can't post for the outcome that you want”

“it rewards consistency over time”

Both hosts are genuine hands-on practitioners - a working CTO writing the code and a CEO running actual sales cycles - with a real enterprise client (World Police Games Perth 2027), which gives the episode grounding; however they are early-stage founders in year two with no proven at-scale outcomes, and there are no external guests at all.

“We are into year two of running a remote starter, sixsides.co, and it's a community led events platform”

“the app is due to be handed over to the police games on August 17”

The episode does surface concrete figures - Maestro device testing at $250/month per device USD, a designer retainer of $15k US ($21k AUD), a hard handover deadline of August 17, five written test cases, a development freeze of August 3 - but these are mostly scheduling and cost details for one project rather than repeatable benchmarks a wider audience could apply.

“I'm talking $250 a month per device US”

“if we're gonna spend 15,000 US, which is 21 k ish Australian”

This is a co-founder check-in, not a hosted interview; questions amount to 'what have you been working on?' with no challenging follow-ups, no probing of assumptions, and no productive disagreement - claims like the LinkedIn strategy pivot or the cold email failure are accepted without any attempt to diagnose why or interrogate the data.

“What have you been working on this week? Last week? Sorry. Yeah. We're recording this on Monday.”

“Yeah. Yeah. Yeah. So Yeah. Yeah. So But it was just the shock of it”