How it feels when six years of work clicks for someone in 30 minutes

A stranger recognized in 30 minutes what I'd been building for six years

On Thursday evening, May 8, I was on a 47-minute Fathom call with Dylan Bindrup, a Squarespace designer based in Farmington, Utah. He runs his own studio, Highr Labs. One hundred-plus sites built. Solo operator. Real clients, ongoing work.

Six years of agency work at Oase Creative. I built Oase Software with co-founder Lam Hoang because I wanted to feel at home in my own tools. That's it.

Then Dylan came in. No briefing read up front, no documentation studied. I walked him through the dashboard. Halfway in he dropped one sentence: "I'm so annoyed about having 50 tabs open." Not a leading question on my side. A stranger on the other side of the ocean described, in his own words, exactly why this product had to exist.

This piece is about how it feels when months of design click for someone in real time.

What he recognized when I showed him

I walked Dylan through the product the way I use it inside my own agency. Four things landed on his face — and I mean landed on his face deliberately, because all of this is visible in the Fathom recording.

Playbooks. In Oase you turn your SOPs into templates that auto-generate tasks at project start. Not a stray Notion page, not a Google Doc nobody opens. Service-specific playbooks that make the system smarter the more you feed it. When I showed that, Dylan's first honest signal arrived. When I asked 40 minutes later, "did you feel that aha moment when I showed you around the software?", he replied: "Yeah, definitely. I mean, I feel like just the playbooks and then creating tasks from the invoices or from just anything." A designer who'd been managing scattered SOPs for years recognized the concept without explanation.

That this is even possible comes down to a layer underneath you don't see. Every project has a timeline — what came before, what came after, what was discussed, what got shipped. Without that timeline layer, an AI agent can't generate a playbook from a finished project. Anyone stitching eight separate tools together doesn't have that context. The agent has to work extra hard, or it just doesn't happen. No timeline, no playbook generation. Architecture first, smart features second.

Services. Designers have been writing one-off proposals for recurring work for years. In Oase, services live as scaffolding that drives quotes and pre-bakes tasks. We don't only do Squarespace, so we have discoveries, package design, multilingual rollouts — all sitting as services in the portal. Dylan can see them in his client portal and re-order them. Second client touch in one click.

Quote to project. An accepted quote automatically creates the project, including tasks pulled from the linked services and playbooks. No manual re-typing, no "oh, I still need to set up the folder." That's not a feature I made up because it sounds cool. That's six years of forgetting every Monday morning to make a task list for a project I sold on Friday.

Form to project, with file system inside. A briefing form the client fills out automatically creates the project with the right folder structure inside. Dylan reacted directly: "I'm actually not very good with, like, organizing project files." His folder mess sat in his downloads folder, not in any nice system. I showed him the auto-folder-creation solves it and he said: "yeah, that's nice." Without me explaining, he saw how the whole thing comes together. That's the entire point.

None of these four features got added yesterday. They were already in the roadmap, designed out of six years of agency practice. Dylan didn't recognize them because they were new. He recognized them because he'd been doing them in four different tabs for years. Dylan's overall reaction to the walk-through: "you guys thought of everything." That's not a pitch line out of our mouths. That's what an outside operator says when the architecture holds together.

You make the aha. You don't find it.

The full call is above. You can watch it yourself. But the question I literally ask around minute 40 is this: "did you feel that aha moment when I showed you around the software?" Dylan's answer: "Yeah, definitely. I mean, I feel like just the playbooks and then creating tasks from the invoices or from just anything. And then also creating content after your projects are done is like the biggest bottleneck for me. Like I hate writing stuff."

Aha moments tend to sound like discovery. What I saw in those 47 minutes was different. Aha moments are made. You show someone something they already knew without knowing it. Dylan had known for years that his workflow was broken. He didn't know a tool could exist where exactly those broken parts were stitched together. The moment he saw it, it clicked.

The product is a mirror of six years of agency work. But it wouldn't work if the pain I was building was only my pain. He's in Utah, I'm in Arnhem. He does Squarespace, I do e-commerce branding. He's solo, I run with freelancers. And still his eyes recognized every button. That's what happens when you build out of real experience instead of a research deck.

Why the Six-Figure Design Club is the right first-ten

Dylan didn't show up through a Google search or an ad. He came in through Sam Crawford. Sam is in Liverpool, has more than 700 Squarespace builds to his name on his site bycrawford.com, and runs the Six-Figure Design Club, a community and course for serious Squarespace and web designers. Dylan is a member. Other designers in the same community get access to the same pilot offer.

For a product trying to find its first ten users, that's worth more than a hundred cold-outbound attempts. One niche. One shared frustration — endless context switching. And a group of people talking to each other every day in a Slack or a community call. What Dylan recognizes, others recognize too.

It's a validation cohort and a champion cohort. Recognition first, distribution second. Dylan and I originally met through Gents Croquet Club, a private members community for cross-disciplinary builders. The Design Club is where the product has to land.

What this validates (and the one thing we're adding)

What he saw wasn't a feature list. What he saw was an end-to-end design software for design agency owners. Not project management with a form tool bolted on. Not invoicing with a chat tab next to it. The whole work of an agency — quote to review to invoice to content — as one connected system.

Looking at it after the call: this is what it's like to be building a product people want, and getting this validation after months of work. Not applause. Recognition. An outside operator who, with no preparation, sees what the thing does and says: yeah, this checks out.

The features Dylan recognized were already designed into the roadmap. Playbooks. Services. Quote-to-project. Form-to-project. Client portal with design review. Dune as the built-in AI agent. App store for extensions. Whiteboards. The V2 roadmap I outlined on top of all that during the call — Stripe Connect, milestone payments, Google Drive integration, social-media scheduler with authentication, capacity planning for teams — is also already mapped.

Dylan summed it up himself: he has to put in some time getting set up, but it'll pay off because so much will run automatically afterward. That's the design exactly.

There is one honest addition. Dylan asked whether clients without an account can fill out a briefing form. In our current model, you need an account to start a form — the system leans on connected data and the form submission auto-creates your project, your folder structure, your playbook tasks. That's a design choice, not an oversight. But Dylan also sends his briefing forms to leads who aren't members yet. Sales use, not onboarding use.

That goes on the V1+ list, not V0. External-client forms open permissions, multi-tenancy and a whole case-handling layer we're not ready for yet. We deliberately scoped V0 to the delivery half of an agency, because delivery is where the most tabs are open. Marketing forms for leads is a separate layer, and it gets built as soon as we can do it without breaking the current flow.

Marketing intelligence — the one thing no competitor has

Dylan also recognized something none of his other tools do: making his own work legible for his own marketing. He said it himself in the call: "creating content after your projects are done is like the biggest bottleneck for me. Like I hate writing stuff." That is the problem. And that is exactly where the marketing intelligence layer plugs in.

Here's the sharpest version: because the software is end-to-end — quote to project to tasks to review to feedback to invoice — Oase owns the full context. No other tool has that data. Bonsai knows what you invoice. Notion knows what you write down. Slack knows what was said. Nobody has all of it. We do.

That is the switch driver. Other tools make Dylan's life simpler. A marketing intelligence layer solves a problem nobody else solves for him. He doesn't have to start from a blank ChatGPT window, build a prompt, and end up with generic copy anyway. He clicks. The system already knows.

It's a feature, not vaporware. But it only works because the architecture underneath holds — and that architecture was there before Dylan walked in. No competitor can build better case studies for design agencies, because no competitor owns the data. That isn't a marketing line. That's what an end-to-end stack structurally enables, and what eight stitched-together tools structurally can't.

Speed is the differentiator, not listening

Honest about who did the talking: me. That's not a scandal, that's a demo. It's not a listening session. It's a walk-through where the operator (me) shows what he built, and the second operator (Dylan) reacts to what he sees. That's a different kind of conversation than "I listened to his needs and built his product." Dylan tried to share an opinion a few times. He didn't have a lot to share, because most of it already checked out.

Put it this way: the fact that you can have this conversation, talk to your programmer the next day, and have it built within the month — that's what a corporate SaaS can't do. Bonsai can't do that. ClickUp can't do that. Asana definitely can't. They have tickets, queues, roadmap managers and four quarters between "customer says something" and "feature is live."

Dylan asked during the call about the USD display that wasn't carrying through in a few places in the system. Small thing, easy to miss, irritating to see daily. By Monday evening, that patch was in. Listening isn't what makes the difference. Every SaaS listens — they're all good at that. The difference is the build time between call and ship.

Founder-built means: conversation today, fix tomorrow, deploy this week. No three roadmap meetings, no "we'll log it as a ticket." Not that I listened better. The build loop is short enough that his question has real-time impact.

For the first ten, that's the entire proposition. Founder as CEO and builder and support. One message, one answer, one commit. That's what a corporate SaaS structurally can't match.

What this means for the first ten

The first ten aren't our research cohort. We already know what we're building. Six years of agency work, months of design, and a product I'm running inside my own agency for real clients. The first ten are here to validate that the building work works, and to widen the product mirror beyond just my own pain.

What Dylan showed in 30 minutes: it works. The features hold up. The mental model clicks without explanation. The next nine are champions. Someone who uses the product, tells their own community about it, and brings in a handful of fresh Squarespace designers. That's how you build distribution without an ad budget.

If you're reading this and you're a design agency owner, a Squarespace designer, a Webflow builder or a brand studio with more than two people, and you recognize yourself in the tab stress Dylan described, here's the simplest route: send me a DM. On LinkedIn or via getoase.com. The first ten spots aren't full. Three months free, in exchange for your honest opinion on what you recognize and what can still be better.

No onboarding funnel. No demo form. A conversation in which I show you what we built, and you tell me whether it clicks. Dylan spent 47 minutes showing me it can click. We're expecting the rest of you this month.