Get AI summaries of any video or article — Sign up free
Founder Fridays: How second-time founders build with Frank Greeff, co-founder of Kinso thumbnail

Founder Fridays: How second-time founders build with Frank Greeff, co-founder of Kinso

Notion·
5 min read

Based on Notion's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Kinso aims to unify business communication across email, Slack, WhatsApp, LinkedIn, and more into one app, then rank messages by inferred user priorities.

Briefing

Kinso’s core bet is that business communication shouldn’t be treated as separate silos—email, Slack, WhatsApp, LinkedIn, Instagram—because the same people and the same relationships drive decisions across all of them. The product aims to ingest those channels into a single app, then use AI to infer what matters most to a user at any moment and stack-rank messages accordingly. The technical centerpiece is not just “better search,” but building AI context that connects related threads across tools, so an AI draft can use the richer, cross-channel history rather than a single-message context window.

That approach is tied to how Frank Greeff and his brother decided to build Kinso after selling Realbase for 180 million. Post-exit reflection reframed “freedom” as the ability to choose which battles to fight, not to stop building. Over a two- or three-month exploration phase, they sampled many business ideas and watched their own enthusiasm rise or fall as they uncovered more data. Kinso won because deeper investigation made the problem feel more exciting—not less—an internal signal they treat as a prerequisite for committing to a long, high-effort journey.

Conviction also came from early traction: a waitlist that reached about 13.5 thousand people, with growth approaching 100 new signups per day. The momentum served as proof that the communication pain point was real and that the market was willing to line up before the full product existed.

Realbase shaped Kinso’s operating philosophy more than its product mechanics. Realbase scaled across Australia and New Zealand to a 47% market share, but it also demonstrated what gets lost as organizations grow: individual accountability and “human” visibility fade. Kinso’s counter-design is a smaller, high-performing team—17 people, all with ESOP/shares—so everyone has a stake and can “win together.” The goal is to recreate the intensity of a small team while still building toward scale.

Hiring and team-building follow the same logic. Greeff criticizes the common practice of judging candidates only against a tiny pool; without enough volume, “best” is just “least worst.” Kinso’s early hiring required about 120 interviews to place eight engineers, creating a clearer measuring stick for what “excellent” looks like. The company also tries to hire for “unfair advantages” rather than generic credentials: ground-level ownership, GitHub autonomy/agency, and fewer layers of middle management.

On the AI side, Kinso leans on agentic workflows and heavy documentation to improve output quality. Engineers use AI coding in parallel—one engineer reportedly runs nine instances of Claude Code simultaneously—while Notion functions as the “brain” of decision-making. Principles for PRDs and other artifacts are documented so AI agents can transform customer feedback into product requirements, then into execution plans for code generation.

Even the founder advice is operational: don’t equate failure with shutting down an ABN; track the individual and whether someone stays in the game. In Greeff’s view, the real determinant is persistence, not a single binary outcome.

Cornell Notes

Kinso is built around a single idea: business communication is fragmented across many apps, but the underlying relationships are continuous. The product unifies those channels and uses AI to infer user priorities, then ranks messages using context that spans email, Slack, WhatsApp, and other tools. The technical challenge is creating “context cards” that connect related conversations across platforms, so AI drafts can use more than one-message context. Kinso’s team strategy mirrors its product philosophy—small, high-ownership groups with strong autonomy—because large organizations lose accountability and clarity. Early conviction came from deep idea exploration and a waitlist that grew to roughly 13.5k with near-100 daily signups.

Why does Kinso treat cross-channel communication as a technical problem rather than a UI problem?

Communication often involves the same people across multiple channels—email for formal updates, WhatsApp for more casual coordination, Slack for internal chatter, and social platforms for visibility. Kinso’s claim is that AI responses improve when it understands the connected relationship between those messages. That requires linking threads and adding metadata across tools into richer “context cards,” so an AI draft for an email can incorporate what happened in WhatsApp or Slack, not just the single email’s context window.

What internal signal convinced the founders that Kinso was worth building after exploring many ideas?

During a two- or three-month exploration phase, they investigated many business possibilities and tracked how their enthusiasm changed as more data came in. The pattern that mattered: the more they uncovered about Kinso, the more exciting it became. That contrasted with other ideas where deeper research reduced enthusiasm—an indicator they used to decide where to commit for a long, high-effort build.

How did Realbase’s scaling experience shape Kinso’s team design?

Realbase scaled to a 47% market share across Australia and New Zealand, but it also illustrated what happens as companies grow: individuals become harder to know, and “humanity gets lost.” Kinso’s response is a smaller team (17 people) where everyone has ESOP/shares, so incentives align and the organization retains clarity and shared ownership. The goal is a high-performing, tightly connected group rather than a large, layered one.

What hiring principle led Kinso to run far more interviews than typical?

Greeff argues that judging candidates against only a few peers creates a misleading “best candidate” outcome—best relative to a small set, not best in absolute terms. Kinso needed enough hiring volume to build a real measuring stick for excellence, which required about 120 job interviews to place eight engineers. The point is to calibrate what “excellent” looks like through repeated selection.

How does Kinso use AI coding and documentation to improve engineering output?

Engineers use AI coding in parallel; one example described nine simultaneous instances of Claude Code. But parallel coding only works well with the right context and frameworks. Notion is used as the “brain” for decision-making, with extensive documentation and principles (e.g., PRD principles rather than just PRDs). Agents then transform customer feedback into PRDs, convert PRDs into game plans, and finally generate code—while relying on senior engineers to remove “slop” from AI output.

What does “unfair advantage” mean in Kinso’s hiring and product go-to-market?

For hiring, it means offering conditions competitors can’t easily replicate at scale: ground-level entry, ESOP, GitHub autonomy/agency, and fewer middle-management constraints. For go-to-market, it means starting with a founder wedge supported by personal brand reach—roughly 15 million eyeballs in the prior 30 days—so the product can reach decision-makers faster than a brand-new accelerator entrant.

Review Questions

  1. How does Kinso’s “context cards” approach differ from using a single-message context window for AI drafting?
  2. Why does Kinso believe hiring requires interview volume, and what does that change about how “excellent” is identified?
  3. What role does Notion play in Kinso’s AI-assisted engineering workflow, beyond general note-taking?

Key Points

  1. 1

    Kinso aims to unify business communication across email, Slack, WhatsApp, LinkedIn, and more into one app, then rank messages by inferred user priorities.

  2. 2

    The product’s main technical challenge is connecting related conversations across tools using richer “context cards,” so AI drafts reflect cross-channel history.

  3. 3

    Post-exit, Frank Greeff and his brother chose Kinso after exploration increased their enthusiasm as more data emerged, treating that as a commitment signal.

  4. 4

    Kinso’s operating model favors a small, high-ownership team (17 people with ESOP/shares) to preserve accountability and shared incentives as the company scales.

  5. 5

    Hiring is calibrated through high interview volume (about 120 interviews for eight engineers) to create a real measuring stick for excellence rather than “least worst” comparisons.

  6. 6

    Kinso uses agentic AI coding workflows (including parallel Claude Code instances) supported by extensive documentation and principles stored in Notion.

  7. 7

    Founder advice centers on persistence: binary “failure” can be misleading if multiple ABNs are tracked, and the key determinant is whether the person stays in the game.

Highlights

Kinso’s AI drafting bet depends on cross-channel context: an email response should benefit from what happened in WhatsApp or Slack, not just the email thread.
Conviction came from both process and traction—deep idea exploration where enthusiasm rose, plus a waitlist that reached ~13.5k and grew by nearly 100 per day.
Kinso’s team philosophy is intentionally anti-bureaucracy: small teams with ESOP/shares to keep “humanity” and accountability intact.
Hiring excellence is treated as calibration, not intuition—Kinso ran roughly 120 interviews to place eight engineers to define what “excellent” means.
Notion is positioned as the “brain” for AI workflows, turning documented principles into inputs for agents that generate PRDs and execution plans.

Topics

  • Business Communication
  • AI Context
  • Agentic Coding
  • Founder Strategy
  • Hiring Calibration

Mentioned