Figuring It Out: How We're Applying an Experimental Mindset to Building a Business as a Duo

We are a two-person team building something new. If you were looking for a polished success story or a case study in "how we hit 10k MRR in three months," you’ve come to the wrong corner of the internet.

Right now, we don't have customers. We don't have a product-market fit. We don't even have all the answers to the questions we’re asking ourselves.

What we do have is an experimental mindset.

We’ve decided to treat this entire process—the building, the role-sharing, the inevitable failures—not as a high-stakes performance, but as a series of laboratory experiments. This article isn't a playbook; it’s a collection of field notes from two people figuring it out in real-time. We’re sharing this because the "messy middle" is where the most interesting growth happens, and maybe, just maybe, it’ll help another tiny team realize that not having a map doesn't mean you’re lost.

The Mindset Shift: From Perfectionist to Experimenter

In our previous lives, we both fell into the same trap. It’s a common one for anyone with high ambition: the Perfectionist Mindset.

The perfectionist needs certainty. They want to know exactly how the script ends before they start filming. When we first started talking about building a business together, that old perfectionism tried to crawl back in. We found ourselves caught in what we call the "Maximized Brain"—the nagging feeling that if we were going to do this, it had to be huge. It had to be an "Epic Script" from day one.

But society’s definition of success often feels like a straitjacket for a two-person team. If you’re not building a unicorn, are you even building?

We decided to push back. We realized that high ambition doesn't have to mean low curiosity. In fact, when you combine high ambition with high curiosity, you get the Experimental Mindset.

Instead of fearing the unknown—the "what if nobody likes it?" or "what if we fail?"—we’ve replaced that fear with a genuine curiosity about what will happen. In a lab, a "failed" experiment isn't a failure of the person; it’s just data. It tells you exactly what didn't work so you can narrow your focus on what might.

We’re not trying to win yet. We’re trying to learn.

Borrowing from Sprint: Structure Without Rigidity

When you’re a tiny team, "process" can feel like a dirty word. You don't want meetings, you don't want spreadsheets, and you definitely don’t want bureaucracy. However, zero structure often leads to zero progress.

To solve this, we turned to Jake Knapp’s Sprint. We didn’t follow it like a religious text—we don’t have five days to lock ourselves in a war room—but we stole the principles that made sense for our scale.

Principle 1: Individual thinking beats groupthink In a two-person team, echo chambers are your biggest threat. It’s so easy to just nod along because you like each other. Now, when we have a problem to solve, we sketch separately first. We come to the table with two distinct ideas, then compare. It forces us to justify our logic rather than just agreeing on the first thing that sounds "fine."

Principle 2: Decide by domain, not consensus Everything is built on trust, but ties need breakers. We’ve split our domains clearly: Alan (CTO) has the final call on all things engineering, and I (CEO) have the final call on product and business strategy. The honest part: This is incredibly hard. I’m technical. Letting go of engineering decisions—even small ones—feels unnatural. But we’ve learned that consensus is slow, and speed is our only real advantage right now.

Principle 3: Prototype before you build We try to "fake it" before we make it. We’re testing the viability of ideas, not the perfection of the execution. If we can validate a hypothesis with a landing page or a manual process instead of a week of coding, we do it.

Principle 4: Compress the timeline We use the same sequence as a traditional sprint—Map, Sketch, Decide, Prototype, Test—but we’ve tightened the loops. We might do this over a few days instead of a full week, but the order remains sacred.

The Pact: Our Version of "Sprints"

Instead of setting rigid habits or massive quarterly goals, we run Pacts. Inspired by Anne-Laure Le Cunff, these are short-term commitments that allow us to move fast without the burden of "forever" promises.

Element	How We Apply It
Duration-bound	We commit for 2 weeks. At the end, we evaluate. No long-term guilt.
Trackable, not measurable	Did we do the thing? Yes/No. We aren't worried about conversion rates yet, just our own consistency.
Purposeful	Each pact is a test for a specific hypothesis about what might work.

Data: External AND Internal

Most business advice is obsessed with the external: revenue, traffic, signups. And yes, those are essential. But they are lagging indicators. For a tiny team, there’s another data set that is far more predictive of long-term success: Internal Data.

Internal data is about energy, dread, and excitement. It’s the stuff that leads to burnout if you ignore it. We use a simple decision matrix to evaluate our experiments:

• High External + High Internal = Keep going. You’ve found the magic.
• High External + Low Internal = Danger zone. This is success that drains you. If it works but makes you miserable, it’s not actually working.
• Low External + High Internal = Worth exploring. Maybe the market hasn't caught up, but the passion is there.
• Low External + Low Internal = STOP. Pivot immediately.

If we're succeeding on paper but hate waking up to do the work, the experiment is a failure. We’re building a business to support a life, not the other way around.

No Customers? Become the Scientist

A common critique of the Sprint methodology is that it requires five customers to test your prototype. But what if you have zero? What if you’re so early that "customers" are still a theoretical concept?

Instead of waiting for an audience, we’ve learned to become the scientists. We use a few workarounds:

• Self-Anthropology: We observe our own lives like scientists in a lab. What gives us energy? What drains it? Where are our "Magic Windows"—those 90-minute blocks of peak focus where we do our best work? We track these patterns and adjust our business experiments to fit our biology, not the other way around.
• Interview the Problem Space: We don't have customers, but we can talk to people who might have the problem we're trying to solve. We’re not pitching; we’re investigating the pain.
• Use Our Own Pain: We are building what we wish existed. If a tool or a workflow solves a real problem for us, it’s a data point. It’s not universal proof, but it’s a start.
• Synthetic Feedback (Via AI): With a healthy dose of skepticism, we use AI to simulate different persona responses to our ideas. It’s not a replacement for real humans, but it’s a great way to catch "low-hanging fruit" errors in our logic.

Procrastination = Data (The Triple Check)

When we get stuck, we don't shame ourselves. We’ve realized that procrastination isn't a character flaw; it’s a signal. It’s data waiting to be decoded. We use what we call the Triple Check to diagnose why we’re dragging our feet:

1. Head (Strategy): Do I rationally believe this is the right thing to do? If the answer is no, we don't need "discipline"—we need to redefine the strategy.
2. Heart (Enjoyment): Am I dreading this specific task? If yes, how can we redesign it to be more fun? Can we turn a boring spreadsheet task into an automation experiment?
3. Hand (Skills): Do I lack the tools or knowledge to do this? If yes, it’s not laziness; it’s a resource gap. We ask for help or dedicate a pact to learning the skill.

Procrastination is often the brain’s way of saying "This experiment is poorly designed." Listen to it.

Collaborating with Uncertainty

The old mindset tells you to eliminate uncertainty. Plan everything. Know the outcome before you invest the effort.

The experimental mindset says: Collaborate with uncertainty.

We can’t know what will work. We can’t know if our current "pact" will lead to a breakthrough or a dead end. But that not-knowing is exactly where growth happens. If an experiment fails, it’s not a personal failure. It’s not even a wasted two weeks. It’s just more data to feed into the next loop.

When you stop trying to control the outcome and start being curious about the process, the pressure lifts. You’re no longer a "failed entrepreneur"; you’re just a scientist who just finished a very interesting experiment.

What We Haven't Figured Out (An Honest List)

We promised field notes, not a playbook. In the spirit of transparency, here are the things that keep us up at night—the puzzles we haven't solved yet:

1. Validation without an audience: How do you truly validate an idea when you don't have a high-traffic funnel to push people through?
2. The "Pivot Point": When do we know if a Pact is truly wrong vs. just needing more time? How many "failed" experiments lead to a pivot?
3. The Epic Script Temptation: How do we stay ambitious and build something meaningful without falling back into the trap of thinking it has to be "huge" to be valid?
4. Role Division reality: On paper, "CEO" and "CTO" sounds clean. In the middle of a Tuesday afternoon, the lines get blurry. We’re still learning how to hold each other accountable without stepping on toes.

Why We're Sharing the Messy Middle

Most business writing happens in reverse. People reach the summit, look back, and write a story that makes it all sound inevitable. They omit the dread, the confusion, and the experiments that went nowhere.

We’re choosing a different path. We’re building in public because we believe there is immense value in showing the process—the messy, unpolished, experimental middle. Maybe you’re also part of a tiny team trying to build something cool. Maybe you’re also tired of the "epic scripts" and just want to figure out what works.

If you are, we’d love for you to follow along. We don't have the map, but we’re having a hell of a lot of fun exploring the territory.

---

Resources referenced in article:

• Sprint by Jake Knapp: The five-day process we’ve adapted for our two-person loops.
• The Experimental Mindset: A look at how to default to curiosity when things get hard (inspired by Anne-Laure Le Cunff).
• Jake Knapp just released Click: A 2-day Foundation Sprint for early-stage projects. Our library hold is pending—we’ll report back once we’ve run our first test with this new framework!