Intempt Handbook

How we run product

Builders, not coordinators.

A clam pressing streams into one pearl

Product managers at Intempt are builders, not coordinators. If you only manage Jira tickets and schedule meetings, this is not the role. PMs here write specs engineers can build from without back-and-forth, prototype in Lovable before engineering picks anything up, and evaluate AI output quality across the product.

How product runs across its three vectors (a differentiated AI product, QA, and customer) is in product operations, and it is graded every week by the product health score.

What product owns

  • Specs engineers can build from without ambiguity. Design and UX decisions
  • AI prompts - write, iterate, evaluate output quality, flag degradation. Prototype in Lovable before engineering touches it
  • Every surface a visitor lands on, and the loop from that surface to a paying workspace: the landing page, the signup, the paywall, and activation
  • Product metrics - adoption, retention, engagement, not just ship dates
  • Incident war room and stakeholder communication during Critical and Major incidents

A PM who only coordinates between teams is not what Intempt needs. Technical fluency is required - enough to work directly in the product, evaluate AI output, and hold engineering accountable to the spec.

Growth: Product & Growth runs the direct channels and the loop to paid

We are a signup ecommerce product, so growth lives in product. Product & Growth runs the direct signup channels and the whole loop to paid: PLG distribution, the creator and UGC program, the paid media on that UGC, and campaigns and coupons. These are the growth experiments and growth programs, PLG plus direct recipe-based UGC ads, detailed in growth channels. Marketing runs the long game off-surface (content, SEO, AEO, social, founder brand, partnerships) and hands the visitor a surface; everything after that is Product & Growth's: the landing page, the signup, the paywall, and the activation that turns a free workspace into a paying one.

Media buying sits here, not on Marketing, because the paid we run is paid on our own creator UGC. Paid runs per feature, not per brand. Each feature that can stand on its own gets its own ads, its own landing page, and its own signup or paywall, and one PM owns that loop end to end: which feature to push, the offer and the price, the page that converts, and the self-serve revenue behind it. The creative is cut from the creator UGC the program produces; the PM owns the surface it points at and the number it moves. It is how a product sells itself one capability at a time.

The one number here is activated free workspaces per week and the self-serve revenue behind them, the same number the growth flywheel reports, and it is graded by the product and growth 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 & Growth, 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: scoring outputs on relevance, accuracy, format, and helpfulness against defined rubrics. Every AI feature ships with a quality bar. If the model output degrades, product catches it first.

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