Venture 03 · LoopLift
Build momentum before launch—and keep learning after it.
LoopLift connects waitlists, feedback, campaigns, customers and product decisions so teams can grow with evidence instead of guesswork.
- Waitlists
- Feedback
- Campaigns
- CRM
- Growth loops
- Stage
- In build
- Portfolio bay
- Bay 03
- Focus area
- Launch & Growth Control
- Part of
- The Collective Foundry
The problem
Why LoopLift exists.
Most teams launch into silence, then guess at what to do next. Demand is not built before launch, and the signal that follows scatters across tickets, calls and dashboards no one owns.
Who it's for
Teams preparing to launch or grow a product who want to build demand and learn from it in one motion.
The opportunity
The market LoopLift is built for.
Every launch produces signal — what customers adopt, ignore and ask for — but most teams scatter it across tickets, calls and dashboards no one owns. As go-to-market shifts to community-led and pre-launch demand building, the tools for capturing and acting on that signal are consolidating.
Why now
The timing behind it.
- 01
Paid acquisition keeps getting more expensive, pushing teams toward owned audiences and pre-launch demand.
- 02
Customers expect to shape products; feedback and roadmaps are now part of go-to-market, not an afterthought.
- 03
AI can finally connect scattered signal — feedback, requests and campaigns — into one continuous loop.
What it does
The capabilities inside LoopLift.
Build demand early
Waitlists, audiences and campaigns that create momentum before the product ships.
Capture the signal
Feedback, feature requests and announcements gathered in one place instead of scattered everywhere.
Nurture & convert
CRM and email journeys that turn early interest into engaged customers.
Close the loop
Continuous learning that feeds what customers say back into the roadmap.
What makes it innovative
Why LoopLift is different.
Demand before day one
Waitlists and audiences turn launch from a cold start into a warm one.
One loop, not silos
Feedback, CRM and campaigns connected so customer signal reaches the roadmap.
Learning that compounds
Every release feeds the next, so growth becomes a loop rather than a spike.
The usual way
Launch into silence, then reconstruct what happened from scattered tickets and calls.
The foundry way
Build demand early and route every signal back into the roadmap in one motion.
How it compares
LoopLift against the feedback, messaging and CRM tools a launching team assembles instead.
Every competitor cell below is drawn from that vendor's own official site on the date shown. Where a capability was not documented there, it is marked Not publicly verified rather than Not available — absence of evidence is not evidence of absence.
| Capability | LoopLift In build — no released tier | Productboard Productboard with Insights and Portal | Canny Free (25 tracked users) through Business (CRM integrations, SSO) | Customer.io Journeys, with Data Pipelines as a separate product | HubSpot Free tier (2 users, 1,000 contacts, 2,000 emails/month, 1 automation) |
|---|---|---|---|---|---|
| Before there is a product Waitlist and pre-launch audience building Demand built before ship. The row that separates this shortlist, because two of the four cannot start until a product exists. | Planned Depth 0/5 · target 5/5 The one row nothing in this shortlist properly occupies — two of the four cannot start until a product exists. It is also the cheapest thing here to build, which is why the venture starts with it. | Not publicly verified Depth 0/5 A post-launch product by design; pre-launch waitlists are not part of its documented scope | Not publicly verified Depth 0/5 Post-launch by design; no pre-launch waitlist or audience surface is documented | Limited Shipped Depth 2/5 Form triggers and real-time segments could implement a waitlist, but no waitlist product is documented — it would be something you assemble | Included Shipped Depth 3/5 Free forms and landing pages with submissions logged straight to the contact database and an automatic follow-up — a waitlist in all but name, with HubSpot branding on the free tier |
| Before there is a product Campaigns that create momentum before launch A waitlist nobody is told about is a form. Reaching an audience is a separate capability from collecting one. | Planned Depth 0/5 · target 4/5 Parity. Customer.io and HubSpot both run campaigns well; the argument is that the campaign and the waitlist share one record, not that the campaign tool is better. | Not publicly verified Depth 0/5 Not documented. The portal reaches existing users, not an audience that does not exist yet | Not publicly verified Depth 0/5 Not documented | Advanced Shipped Depth 5/5 Cross-channel journeys across email, push, in-app, SMS, WhatsApp, Slack and webhooks, with branching logic and one-time or API-triggered broadcasts | Included Shipped Depth 4/5 Landing pages, forms and email on the free tier, with page content varying by location, device, lifecycle stage or stored contact detail |
| Learning from users Feedback and feature requests captured from everywhere Signal arrives in calls, tickets and chats, not in a feedback form. Capture breadth decides how much of it is ever seen. | Planned Depth 0/5 · target 4/5 Parity with Canny, whose Autopilot already reads eleven named sources plus review sites. Matching that breadth is the bar, and beating it is not the plan. | Advanced Shipped Depth 5/5 Feedback consolidated from support tools, CRMs and surveys; Spark sorts it and links it to product ideas, with smart topic detection and insight trends | Advanced Shipped Depth 5/5 Autopilot reads Gong, Intercom, Slack, Zendesk, Help Scout, Freshdesk, Zoom, tl;dv, Fireflies, Fathom and Grain, plus G2 and Capterra — with merging and product-area routing | Not publicly verified Depth 1/5 Events can carry anything, including survey responses, but feature-request capture and management are not documented | Limited Shipped Depth 2/5 Forms and live chat capture input into the contact record; feature-request management is not what the product is for |
| Learning from users Prioritising by impact, effort and revenue Turns a pile of requests into an order of work. Mature in this category, and not a reason anyone switches. | Planned Depth 0/5 · target 3/5 Conceded. Productboard’s weighted strategic drivers and Canny’s revenue weighting are both mature, and nobody switches platforms over this row. | Advanced Shipped Depth 5/5 Custom weighted score per feature against stated strategic drivers, a value-versus-effort matrix, and features tied back to company objectives | Advanced Shipped Depth 5/5 RICE and impact/effort scoring, plus weighting requests by the ARR, MRR or opportunity value of the customers who asked for them | Not publicly verified Depth 0/5 Not documented and not in scope | Not publicly verified Depth 0/5 Not documented and not in scope |
| Learning from users Public roadmap and customer-facing portal Whether customers can see where their request went without asking someone. | Planned Depth 0/5 · target 4/5 Parity. Both feedback vendors here score 5, and a portal is a well-understood surface rather than an open problem. | Advanced Shipped Depth 5/5 Portal with voting and submissions, public roadmap, custom branding and domains, and multiple portals for different products or segments | Advanced Shipped Depth 5/5 Internal and public roadmaps that update as statuses change and email followers; public boards suggest duplicates at submission | Not publicly verified Depth 0/5 Not documented and not in scope | Not publicly verified Depth 0/5 Not documented and not in scope |
| Turning interest into customers Lifecycle email journeys The mechanism that converts early interest into a customer, and the one most launch teams run from a separate tool. | Planned Depth 0/5 · target 4/5 Parity on email lifecycle for a pre-launch and early-growth audience. Parity with Customer.io across seven channels is not a realistic target and is not claimed. | Not publicly verified Depth 1/5 Notifies users about features they requested; no lifecycle journey builder is documented | Limited Shipped Depth 2/5 Changelog subscriber emails and follower notifications on paid plans — transactional product updates rather than a journey builder | Advanced Shipped Depth 5/5 The reference point: visual journey builder, segments from profile data, events and behaviours updating in real time, branching paths, and LLM actions inside an automation | Included Shipped Depth 4/5 Email with templates and Workflows for automation. The free tier caps 2,000 emails a month and one automation; the broader sequence tooling is paid |
| Turning interest into customers CRM: contacts, deals and revenue context Without it, feedback cannot be weighted by who said it. With it, this becomes a crowded market against a free incumbent. | Planned Depth 0/5 · target 3/5 The lowest target in the table, and honestly so: HubSpot gives a CRM away free and competing with free is not a plan. Enough contact and revenue context to weight feedback, no more. | Limited Shipped Depth 2/5 Integrates with CRMs to pull customer context onto feedback; it is not a CRM and does not present itself as one | Included Shipped Depth 3/5 Salesforce and HubSpot integration links feedback to deals and ARR on the Business plan; Autopilot can attach an open opportunity, with stated conditions | Included Shipped Depth 3/5 Identity management and profiles, with Data Pipelines doing reverse ETL out to Salesforce and HubSpot. A customer data platform rather than a CRM | Advanced Shipped Depth 5/5 The category reference point, and free: two users, 1,000 contacts, deal pipelines and a reporting dashboard with no expiry |
| Closing the loop Telling the person who asked that it shipped The step that makes people keep giving feedback. Cheap to do, and usually spread across three systems that never speak. | Planned Depth 0/5 · target 5/5 The product’s own claim. It is also the only row where owning both ends genuinely matters, because today the waitlist and the roadmap sit in different systems that never reconcile. | Included Shipped Depth 4/5 Notifies users when there is an update on a feature they requested, which is the loop closed at the portal | Advanced Shipped Depth 5/5 Feedback linked to changelog entries with subscribers notified, and a Slack notification to the account owner when a linked feature ships | Limited Shipped Depth 2/5 Can deliver the announcement to exactly the right segment, but holds no record of what any of them asked for | Not publicly verified Depth 1/5 Can email a segment, but holds no feature-request record to close the loop against |
Who each tool is actually best for
- LoopLift In build — no released tier
Not yet a buying option. LoopLift is in build inside the foundry; the scope below is intent, not shipped capability. The intended buyer is a team at the point where a waitlist, a feedback board, an email tool and a CRM would otherwise be four separate decisions.
- Productboard Productboard with Insights and Portal
Product organisations with more feedback than they can read. Weighted scoring against stated strategic drivers is the most rigorous prioritisation model in this shortlist.
Source: Prioritize features — weighted scores against strategic drivers, value-versus-effort matrix, features tied to objectives , Product portal — voting, submissions, public roadmap, and notifying users when a requested feature updates , Customer insights — feedback consolidated from support tools, CRMs and surveys, linked to product ideas
- Canny Free (25 tracked users) through Business (CRM integrations, SSO)
Teams who want the whole post-launch loop working this week. Capture breadth is the widest here, and a free tier carries feedback, roadmap and changelog together.
Source: Autopilot — captures from Gong, Intercom, Slack, Zendesk, Help Scout, Freshdesk, Zoom, tl;dv, G2 and Capterra, with merging and routing , Product management — Jira, Linear, GitHub, ClickUp, Azure DevOps and Asana; Salesforce and HubSpot on Business; MCP server , Changelog — Fireflies, Fathom and Grain as Autopilot sources; CRM opportunity linking; Customer Requests and Churned Revenue reports , Feature request management — public boards with voting and duplicate suggestion at submission
- Customer.io Journeys, with Data Pipelines as a separate product
Anyone whose problem is the message rather than the roadmap. Seven channels, real-time segmentation from events, and branching that gives each person a different path.
Source: Journeys — cross-channel automation across email, push, in-app, SMS, WhatsApp, Slack and webhooks, with branching and LLM actions , All features — segments from profile data, events and behaviours, updating in real time; segment, event, form, date and webhook triggers , Data Pipelines (CDP) — standalone, with reverse ETL and destinations including Salesforce and HubSpot
- HubSpot Free tier (2 users, 1,000 contacts, 2,000 emails/month, 1 automation)
Almost any team at the start. A CRM, forms, landing pages and email for nothing, with the contact record shared across all of them — which is the same architectural argument LoopLift makes.
Source: Free CRM — two users, 1,000 contacts, deal pipelines, reporting dashboard, no expiry , Forms — drag-and-drop builder, submissions logged to the contact database, automatic follow-up email on the free tier , Landing pages — templates and editor, content varying by location, device, lifecycle stage or CRM contact detail , Marketing Hub pricing guide — free plan limits on email volume and automation
Considered and excluded
- Featurebase, Frill and the other feedback tools — Productboard and Canny are compared as the representatives of this category — the most rigorous on prioritisation and the widest on capture respectively. The others sit between them and would move no row, since none of them crosses into pre-launch either. Check current status
How this comparison is made
- Comparative claims follow ACCC guidance: they must be accurate, fair and supportable on reasonable grounds, judged on the overall impression rather than line by line.
- A competitor capability is only marked as present where its official site or documentation describes it. Where it was not documented the status is “Not publicly verified” — not “Not available”. This is a desk review of published material, not a hands-on benchmark.
- Nothing competes with LoopLift as a whole, so the comparison is against what a launching team actually buys: a feedback tool, a messaging tool and a CRM. Productboard and Canny represent feedback and roadmaps, Customer.io lifecycle messaging, HubSpot the CRM and demand-capture end. Dedicated waitlist tools such as Prefinery and LaunchList were considered and left out — they occupy one row and are a feature, not a platform.
- The pre-launch half is genuinely unoccupied. Productboard and Canny both score zero on waitlists and pre-launch campaigns, because both are post-launch by design and need a product and users before they do anything. HubSpot comes closest at 3/5, since free forms and landing pages logging to a contact record is a waitlist in all but name — and HubSpot is also the hardest competitor here, because it makes the same architectural argument LoopLift does and charges nothing for it.
- Depth scores (0–5) are our own analytical assessment of how deep a capability runs. They are not vendor-published figures, and they are separate from the evidence status beside them.
- LoopLift is in build. Its public address is an intro page, not a released product, so every one of its cells shows delivery “Planned” and an achieved depth of zero. A row moves to “In build” only when there is internal evidence behind it, and its achieved depth is then capped at 2.
- Targets are published only for our own column and only with a stated reason. Two are conceded outright: prioritisation at 3/5 against two vendors scoring 5, and CRM at 3/5 against a company that gives one away free. Two are set at 5: the waitlist row that nothing here occupies, and closing the loop, which is the product’s own claim.
The approach
How we build it.
LoopLift is an AI-powered growth and product intelligence platform for companies preparing to launch or grow a product. It builds demand before launch, learns from users, and turns every signal into momentum.
It brings together waitlist creation, pre-launch audience building, user feedback and feature requests, roadmaps, product announcements, campaign orchestration, email journeys and CRM.
The outcome: a continuous feedback loop between your market and your roadmap.
The outcome
What changes when it's in place.
- Launch day starts with an audience, not silence.
- Customer signal reaches the people who decide what to build.
- Growth becomes a loop, not a one-off spike.
How it fits the foundry
A venture, not a department.
LoopLift moves through the whole foundry — discovery, design, engineering, quality and launch — like every venture we build. It's most visible in Launch & Growth Control, where its business purpose is sharpest.
- Discover
- Define
- Design
- Build
- Assure
- Launch
- Learn
- Scale