Users & roles
Team directory, roles, and access requirements.
Select the modules your team needs, try a workflow and see how the scope affects an example budget. Save an outline for the project discussion without creating an account.
An example replaces the selected features. Your outline notes stay in place.
Select a feature to add or remove it. Required features are included automatically.
Add modules and map the planned data flows. Open a demo to try the supported interactions.
Architecture · Common interface · Delivery setup · Baseline quality checks — counted once
Team directory, roles, and access requirements.
Customer records, deal budgets, and pipeline stages.
Customer access to orders, documents, and requests.
Customer orders, progress, and fulfilment.
Stock levels, reservations, and replenishment.
Metrics, filters, dashboards, and exports.
Connections show how modules should share data. Only the flows supported by the demo update its sample records. Adding a connection does not change this example budget.
Try the features with sample records. The system builder remains above the demo.
Add a demo company or change a stage. Connected reports and recommendations use these same records.
Answer any of these three questions, then download an outline for your team. It includes your selected features and example budget.
Horizon Dynamics — Project outline Project discussion draft Starting scenario: Custom configuration Business goal To discuss Current systems To discuss First-release priorities To discuss Open questions To discuss Assumptions to validate To discuss Outside the first release To discuss Acceptance checks and reviewer To discuss Operating responsibilities and constraints To discuss Solution Studio configuration Modules: Users & roles, Clients & CRM, Customer portal, Orders, Inventory, Reports Scope options: None Connections: Users & roles → Clients & CRM; Clients & CRM → Customer portal; Clients & CRM → Orders; Users & roles → Inventory; Clients & CRM → Reports; Orders → Inventory; Orders → Customer portal; Orders → Reports Example budget: $63,900–$102,600. Not a quote. Connections describe intended flows and add no cost. Discovery, detailed design, source-specific integrations, data cleanup, release validation and rollout are scoped separately. The shared foundation is counted once. Full projects start at USD 50,000. Required paid support, client-paid hosting, licences, paid APIs and taxes are outside this build budget. Priorities above are discussion notes. They do not split the estimate into delivery phases. We agree requirements, dependencies, acceptance criteria, team, and schedule before a proposal. Warranty terms and new development are agreed separately from ongoing support. Next step: discuss the workflow and unknowns, agree any paid assessment, then review a scoped proposal. Planning examples: /pricing/sample-brief · /pricing/planning-example Demo customer, document, order, and transaction records are excluded from this outline.
Notes stay on this page until you download or print them; reloading clears them. The selection link contains features and connections only, without your notes or demo records.
Ready to talk? Use “Discuss this workflow” or “Discuss this configuration” to take your selection to our contact form. You can add your notes there.