Two Operators, One Bet: How Second Brain Started

8 min readJordan Kwan
Two founders, one from the online world and one from brick-and-mortar, working late at one bench the night Second Brain started

Second Brain exists because two people who came up on opposite sides of business, one online, one brick-and-mortar, finally stopped talking about working together and tested whether they could. The test was unglamorous: learn to build, sell the work by phone, deliver it ourselves. It worked faster than either of us expected, and everything we publish here is the working detail of how.

Every consultancy has an about page. Most of them are written backwards from the company the founders wish they ran. This is the forward version: what each of us had actually done before Second Brain, what we built first, and the stretch of work that turned two freelancers with a shared idea into a company with a client roster. It is also the honest answer to the question this blog has to earn: why should an operator trust implementation advice from us? Because this company is itself one of our builds, and its first ninety days are the case study the rest of the feed keeps referring back to.

What did each founder bring?

Complementary gaps, mostly.

Jordan's side was the internet. He built Reachium, a cold-outreach SaaS, and before that ran a string of side hustles growing up: always making money online, never quite making it succeed. The pattern was real skill at pieces of the game, distribution, tooling, persistence, without the thing ever compounding into a business.

Mike's side was physical. He ran a small landscaping company and a painting franchise: crews, quotes, seasonality, customers who pay late, the full education brick-and-mortar gives you in how service businesses actually run. Then he moved into the online space with that operator's eye intact, which turns out to be the rarer combination. Plenty of people can build a funnel. Fewer have stood in a driveway explaining a quote.

We had talked for years about starting something together. Talking is cheap and we both knew it, so the first real decision was not what to sell. It was to run an experiment that would tell us whether we worked well as a team before either of us bet anything serious on it.

What was the first thing they built together?

A travel site neither of us had any business running.

The first joint offer was called Travel Anywhere, and it existed for exactly one reason: it was a vehicle. Jordan needed to learn how modern websites and code actually get built, Mike needed the same reps, and we both needed to find out how we divided work, argued about decisions, and shipped under mild pressure. The travel business itself was never the point, and it never became one. What it produced was a working team: two people who had finished something together and knew each other's pace.

That sequence, prove the partnership on something disposable, then build the real thing, is the same advice we now give clients about their first system. Start with the build that teaches you how the work goes, in the accounts you own, before the build the business depends on. We took our own advice before we knew it was advice.

Where did the clients come from?

Cold calls, then connections.

After the travel experiment, Mike did a lot of cold calling: selling websites on his own at first, and calling for what became Second Brain. There was no launch, no list, no audience. There was a phone, a script that improved every week, and the willingness to hear no at volume. The first clients came from that grind and from the connections around it, and the roster accumulated the way service businesses actually grow: one engagement delivered well enough that the next conversation started warm.

The work ethic is not a poster value for us. It is the literal mechanism the company grew by, and it is why this blog writes about systems the way it does. A system is what you build so the grind compounds instead of resetting every morning. The five-minute callback playbook is a cold-calling lesson wearing software: the person who responds first and follows up properly wins work that better-funded competitors lose, and software is how a small team keeps that standard on its worst day, not just its best one.

How fast did it come together?

From no revenue to around $10K a month in about three months, doing the work we still do: AI implementation, custom software builds, and consulting companies on how to use and optimise AI in their operations.

We state that the way it deserves to be stated: it is our own figure, from our own books, for a services business two people were working full time, not a benchmark and not a promise about anyone else's timeline. What made the run possible was not a secret. It was ninety days of consistent work, an internet connection, and an offer built on skills we had each spent years accumulating separately. The compounding looked sudden from outside. From inside it was the least sudden thing in the world.

That run is also why we push back when implementation gets sold as magic. Our position, argued with data in ranking is not enough anymore, is that the tools are now the easy half. The scarce half is operators who have done the unglamorous parts themselves: sold the work, built the system, answered for it when it broke. AI implementation rewards exactly that profile, which is the whole reason two people with our backgrounds ended up here.

What is this blog for?

Three things, in order.

First, to give away the implementation detail. Most of what we publish is the working layer of real builds: the intake design, the routing rules, the costs with the lines showing, as in our pricing of one AI system four ways. If a reader could not act on a post, or argue with it specifically, it did not do its job.

Second, to publish the numbers we can stand behind. Where we have run a study ourselves, like asking ChatGPT about 40 local service businesses and checking every claim it made, we publish the method with the result. Where we do not have a number, we say so instead of borrowing one.

Third, to be findable by the people the work fits: service businesses whose problem is not effort but systems. If that is you, the fastest way to test whether we are worth talking to is to read the work, then ask us for the audit at the bottom of this page and judge the reply.

Key Takeaways

  • Second Brain was founded by two operators with opposite backgrounds: one from online business and outreach software, one from brick-and-mortar service companies.
  • The first joint project, a travel site, was a deliberate test of the partnership, not a business. Proving the team came before betting on the company.
  • The client roster grew from cold calling and connections, not from an audience or a launch.
  • The company went from no revenue to around $10K a month in about three months of full-time work. That is a first-party figure about a two-person services business, stated as ours, not as a benchmark.
  • This blog publishes implementation detail and sourced numbers because the company's own story is a systems story, and the feed is where we show the working.

FAQ

What was Travel Anywhere, the first project?

A travel site the founders built together before Second Brain, kept deliberately disposable. Its job was never the travel business. It was to teach both founders how websites and code get built and, more importantly, whether they worked well as a team, before anything real rode on the answer.

Who founded Second Brain?

Jordan Kwan and Mike Shields. Jordan built Reachium, a cold-outreach SaaS, after years of online side hustles. Mike ran a landscaping company and a painting franchise before moving into online business. The two had talked about working together for years before running their first joint project.

What does Second Brain actually sell?

AI implementation, custom software builds, and consulting on how companies use and optimise AI in their operations. The work is done-for-you: we design, build, and help run the systems, and this blog documents how those systems work.

Why publish the origin story on a blog about implementation?

Because the claim behind every post here is that we are operators, not commentators, and a claim like that should come with its evidence attached. The company's first ninety days, cold calls, a throwaway first project, a roster built one engagement at a time, are the evidence. The posts that follow are the detail.

Sources

  • Founder account recorded by Jordan Kwan and Mike Shields together, October 2026: backgrounds, the Travel Anywhere project, the cold calling period, and the first three months of revenue. First-party material, quoted and paraphrased with the founders' own figures kept approximate where they stated them approximately.

We source every figure here the way our editorial policy describes: traceable to a named source, or left as an open gap. More on who writes and fact-checks this blog.