Seed · AI SaaS
FlowPilot AI connects WeCom, tickets, and knowledge bases into an automated support workflow.
FlowPilot AI serves China enterprise support teams by connecting WeCom, ticket workflows, and knowledge bases with AI. The goal is to convert repetitive support cost into measurable response efficiency. The project has passed RoundDock basic screening, while core materials require verified capital-side access.
Why this may deserve the next review step
Project storyThe team starts with China enterprise support workflows, focusing on WeCom support, ticket routing, knowledge retrieval, and repetitive Q&A cost.
Current tractionMRR RMB 280k and 26 enterprise customers; MRR screenshots, customer sampling, and contract definitions still need verification.
Use of fundsSales team expansion, model evaluation cost, enterprise integrations, and customer-success workflow.
Best-fit capital-side clientEarly SaaS investors who accept enterprise sales cycles and understand AI-tool retention and integration depth.
Data-room index and verification items
PreparedDeck, product demo video, customer-case summaries, knowledge-base workflow, and basic financial definitions.
To completeMRR screenshots, customer sampling, model-call cost, renewal cohorts, and enterprise sales-cycle breakdown.
Access gateCapital-side clients complete identity, ticket size, sector preference, and risk tolerance first; founder and platform approval still required.
What can be reviewed now, and what is not yet a conclusion
In the packageProduct demo, support-flow map, customer-case summaries, basic financial definitions, and founder-team notes.
Still to verifySubscription revenue versus implementation fees, customer sampling, renewal cohorts, model-call cost, and enterprise sales cycle.
No conclusion yetNet retention, LTV/CAC, long-term gross margin, and scalable sales efficiency require a fuller data room.
Key questions surfaced before a private roadshow
Does MRR include one-time work?Subscription revenue, implementation fees, and custom integration fees should be separated before judging repeatability.
How deep is enterprise integration?Review WeCom, ticketing, knowledge-base, human-review, and customer-success workflows rather than demo quality alone.
Can model cost erode margin?The data room should add usage volume, human review ratio, knowledge-base maintenance cost, and margin sensitivity by customer size.
Key risks are listed before access
Customer concentrationRevenue share from top customers, renewal stability, and sector dependency need verification.
Enterprise sales cycleTrial-to-deployment and deployment-to-renewal cycles should be segmented by customer type.
Model costModel calls, human review, knowledge-base maintenance, and enterprise integration cost need evidence.
Project updates
This weekMRR screenshots and customer sampling are being completed before verified capital-side summaries open.
Next weekProduct demo video, enterprise integration workflow, and model-cost breakdown move into review.
Before roadshowQ&A list will cover customer concentration, renewal quality, and sales-cycle evidence.