Teaching scope
Identify the classes, subjects and faculty workflows for the evaluation. Decide which outcomes you want to observe during a demonstration or agreed pilot.
Institutional evaluation
Define the scope before comparing the price.
An institution needs to evaluate teaching fit, operational requirements and commercial terms together. Request a proposal based on your intended use; no public price or free-trial entitlement is implied here.
A proposal starts with a shared brief
Tell us which departments are evaluating Acadyna, the approximate teaching scope, and the workflows that matter most. Avoid personal student data. We will use your enquiry to clarify requirements rather than enrol you into a mailing list.
Operational fit
Discuss onboarding, class administration and support expectations. Existing institutional systems, access rules and export needs should be checked rather than assumed compatible.
Commercial review
Ask for the inclusions, exclusions, term and responsibilities in writing. This website does not establish a licence, service-level agreement or institutional partnership.
What determines the proposal?
The intended scope and requirements need review with the Acadyna team. No approved public price list is published here. Submitting this form does not create a purchase or activate a paid service.
What should our evaluation include?
Choose one representative lesson, one student interaction and one assessment-review workflow. Test the relevant permissions and use synthetic data before introducing real class records. Ask which requested capabilities are currently available in the proposed configuration.
Who should participate?
Include a faculty representative and the people responsible for institutional technology, procurement and privacy as appropriate. Any compliance, integration or contractual requirement needs explicit verification; it should not be inferred from a product demonstration.