Intempt Handbook

How we run Product & Community

The product is the growth engine. Product & Community owns everything permanent that compounds: the product, every surface, the community that turns users into feedback and evangelism, and the design that makes it feel inevitable.

We are a signup product, so the product is the growth engine, not a thing a campaign points traffic at. Product & Community, led by Aman, owns everything that is permanent and compounds: the product itself, every surface a visitor lands on, the community that turns users into a feedback loop and a volunteer sales force, and the design that makes all of it feel inevitable.

The split with Marketing & Growth is a split by shelf life. Growth rents attention and runs this-week experiments. Product & Community builds the asset those experiments convert into, and it keeps building after the campaign ends. Growth gets a person to a surface; the moment they land, they are ours.

The full strategy across all four teams is in how growth works. It is graded every week by the product health score.

The thesis

A product that sells itself beats a company that sells a product. Every other channel is rented. The surface, the activation, the brand a user trusts on their tenth visit, and the community they stay for are the only assets that compound, and they all live here.

Three beliefs run the team:

  • Permanent beats disposable. A landing page a growth experiment throws away did its job in a week. A surface that still converts in a year is worth a hundred of them. We build the second kind.
  • Community is a product organ, not a megaphone. The people in the Slack, Discord, YouTube, and Reddit are the first to hit a bug, the first to ask for the next feature, and the ones who recommend us unpaid. That loop belongs next to the people who can act on it, not next to the people who buy attention.
  • Design is how trust compounds. Brand is long-term the same way the product is. A banner expires. A brand system on a permanent surface is the thing that makes a stranger believe us.

What Product & Community owns

Product

Owned by the Product Owner, with the Solution Engineer on the customer edge. Specs engineers build from without back-and-forth, design and UX decisions, AI prompt quality, and the roadmap. PMs prototype in Lovable before engineering picks anything up, and they evaluate AI output against a defined quality bar. If the model degrades, product catches it first.

Every surface and the loop to paid

Every surface a visitor lands on, and the loop from that surface to a paying workspace: the landing page, the signup, the paywall, and the activation that turns a free workspace into a paying one. Growth optimizes to activation; we own what activation is. Their pages are disposable; ours are permanent.

Community: feedback and evangelism

Owned by the Community Manager. The Slack, Discord, YouTube, and Reddit communities, run as the product's feedback loop and its evangelism engine. This is not top-of-funnel social reach, which is Marketing & Growth's. It is the users who are already in: surfacing their bugs and feature requests to the people who can fix them, and growing the advocates who recommend Intempt without being paid.

Quality

Owned by QA, led by Tarif. The product works, every release, before a customer sees it. Quality is a product function here, not an engineering afterthought, because the surface that converts is the surface that works.

Design and brand

Owned by Aurobind Venu, with the Design Engineer and the Illustrator & Motion Designer. The brand and every surface's visual system, product design across the console and apps, and the long-term brand on the permanent surfaces. The Creative Director sets the brand direction; design executes the system. Brand lives here because brand compounds, the same as the product.

The one number

The revenue the product's agents generate for customers, attributed to the agent and to Intempt. That is the game: the product is measured on the revenue its agents create, not just on activation. Activated workspaces that stay are the leading input; agent-generated revenue is the number. We grade it every week next to the marketing and growth health score, the engineering health score, and the sales and customer success health score.

We run our own growth on our own product

Every visit to intempt.com and every console session is tracked into one Intempt project, and we use our own segments, personalizations, and experiments to move a person from browse to signup to activated. If a feature is good enough to sell, it is good enough to run our own growth on. It is an internal project, run by Product & Community, and it is the reference example for how a customer runs this.

AI-native product work

PMs cowork with Claude on claude.ai for spec writing, user research synthesis, and competitive analysis. Prototypes are built in Lovable before engineering touches them. AI quality evaluations score outputs on relevance, accuracy, format, and helpfulness against defined rubrics. Every AI feature ships with a quality bar.

Incident role

During Critical and Major incidents, product is in the war room from minute zero. PMs own status page updates, stakeholder communication, and post-incident summaries. This is organizational judgment, not a support role.

Customer support

Customer support is AI-first. Product handles escalated tickets that AI cannot resolve, typically complex product questions, billing edge cases, or account-level issues. Product reviews unresolved tickets as part of normal work, not as an additional burden.

On this page