Reference Paths
Clients need more than features. They need a path that makes sense.
Mature platforms use case structure to make workflows understandable. RoundDock uses reference paths to show how different project types prepare evidence, enter scorecard review, open a data room, schedule roadshows, and route to advisors without implying a financing result.
These are operating examples and project-format demonstrations. They are not financing success claims, investment advice, endorsements, return promises, or actual investment results.
Three reference paths
AI B2B service project
Fits projects with pilot customers, measurable time or cost savings, and a clear delivery workflow. Path: demo access -> customer pilot record -> scorecard -> verified data room -> private roadshow.
Cross-border ecommerce / supply chain
Fits projects with orders, suppliers, inventory turnover, and ad data. Path: redacted store/order proof -> margin and inventory file -> risk labels -> data room -> service-fee invoice.
Local service / chain project
Fits projects with unit economics, contracts, site access, or repeat data. Path: unit model -> cash flow -> expansion use of funds -> advisor review -> regional capital-side roadshow.
Path Blueprint
How a project path is organized
1. Public storyExplain the project, customer, stage, and use of funds without exposing sensitive materials.
2. Evidence packOrganize screenshots, contracts, orders, data, licenses, financials, and videos into a data-room index.
3. ScorecardReview demand, traction, team, use of funds, data room, and risks without forecasting returns.
4. Capital-side matchMatch verified capital-side clients by sector, ticket size, region, risk preference, and access level.
5. Roadshow questionsPrepare the most likely capital-side questions and turn public answers into updates.
6. Professional routingFormal agreements, escrow, taxes, equity, and fund settlement stay with counsel, accountants, or licensed providers.
What trust problem this solves
FoundersKnow which evidence to prepare instead of only writing a vision.
Capital-side clientsKnow why a project may be worth a next look and what remains unverified.
PlatformCan route each project type through a consistent workflow and reduce repeated explanation.
AdvisorsKnow which part they enter without blending their role with platform boundaries.