Practitioner, school, platform, and sales workflows
Choose the right Vedastram entry point for repeated client work, teaching, team access, integration, API, or a product demonstration.
Questions this guide answers
- Which workflow is right for an astrologer?
- How should a school use sample data?
- What should I include in a sales or integration request?
Before you begin
- A clear audience, expected workflow, approximate user volume, and privacy or integration requirements.
Step by step
- 1
Choose the audience path
Use practitioner guidance for client work, school guidance for teaching, and platform guidance for integration or embedded capability.
Expected result: The selected practitioner, school, or platform entry point presents its audience-specific information.
- 2
Describe the job, not only the feature
State whether you need client management, report delivery, classroom demonstration, team controls, API access, or an integration.
Expected result: The brief names the concrete workflow needed rather than only a product feature.
- 3
Estimate scale and sensitivity
Include expected users, profiles, reports, locales, and whether real client or student data will be processed.
Expected result: The brief records expected users, profiles, reports, locales, and whether personal data is involved.
- 4
Contact sales with a safe brief
Use the relevant intent and include business contact, goal, timeline, and technical constraints. Do not email real birth records or report content.
Expected result: The sales brief contains the business contact, goal, timeline, and constraints without private chart or report content.
- 5
Validate with a synthetic pilot
Prove the workflow using synthetic profiles, permissions, exports, locale behavior, and retention expectations before live data.
Expected result: The pilot demonstrates permissions, exports, locale behavior, and retention using synthetic profiles only.
Practitioner workflow
Use Clients for lifecycle management, active-profile safety, consultation follow-up, and archive. Use saved reports and delivery actions for durable client artifacts.
Plan access and practitioner features are shown in the live product and pricing surfaces.
School workflow
Teach with synthetic charts and clearly label the ayanamsa, node, house, and Dasha conventions. Separate calculation demonstration from personal prediction.
Use projection-safe layouts, captions, transcripts, and multilingual terminology governance.
Platform and integration workflow
Define data flow, authentication, rate, latency, calculation settings, auditability, locale, support, and deletion before discussing an API or embedded surface.
A contact-sales acknowledgement is not a promise that a particular API is generally available.
Troubleshooting and recovery
An audience URL returns to the main landing page
That route is an audience entry point. Use the highlighted section or contact-sales intent rather than expecting a separate product.
A request needs private sample data
Replace it with synthetic fixtures and describe the schema or failure. Share real data only through an explicitly approved secure process.
Frequently asked questions
Is there a public API I can start using immediately?
Do not assume availability from the platform page. Use the current integration or sales path to confirm supported access, terms, and technical scope.
Terms used in this guide
- Pilot
- A bounded validation of workflow, permissions, data handling, and outcomes before broader rollout.
Did this guide help you complete the task?
Owner: Vedastram Product Education