Engagement Models
Choose the Right Way to Work with Ayurvite
Begin with a focused consultation, commission a defined assignment, develop a complex project in phases or retain continuing advisory support according to the clarity, scale and duration of your requirement.
Select according to your present stage
01
Early Idea
Use a focused strategy session to clarify the problem, alternatives and next professional step.
02
Defined Requirement
Commission a fixed-scope report, document, website, module or professional assignment.
03
Complex Project
Break consultancy, development and implementation into controlled phases and milestones.
04
Continuing Need
Use monthly advisory, maintenance or product-growth support for ongoing continuity.
Every engagement is confirmed through a written scope covering deliverables, assumptions, responsibilities, timeline, commercials and exclusions.
Defined Scope
Deliverables and boundaries confirmed before work begins
Phased Delivery
Large requirements divided into manageable milestones
Clear Ownership
Client and Ayurvite responsibilities documented
Flexible Continuity
Advisory, maintenance and expansion available
Why the Engagement Model Matters
The right commercial structure should match the certainty and complexity of the work
An early idea cannot be priced reliably like a fully defined software module, while a recurring advisory need should not be managed as a sequence of disconnected one-time assignments.
Selecting the correct engagement model protects both parties from unclear expectations, uncontrolled revisions, unrealistic timelines and avoidable cost escalation.
01
The requirement is still evolving
Begin with discovery or advisory before committing to a large fixed project.
02
The output is already clear
Use a fixed scope with defined deliverables, review cycles and completion criteria.
03
Multiple systems or teams are involved
Use phased delivery with dependencies, milestones and formal acceptance.
04
Support is required after launch
Use maintenance, monthly advisory or a product-growth plan for continuity.
Core Engagement Models
Select the model that best matches your present requirement
The final scope, timeline and commercials are confirmed only after reviewing the requirement, available inputs, dependencies and expected outcome.
01
Strategy Session
A focused professional discussion for ideas, decisions, comparisons and next-step clarity.
- Pre-session requirement review
- Structured online discussion
- Key observations and recommendations
- Suggested next professional step
02
Fixed-Scope Assignment
A defined report, document, website, research output, toolkit or technical deliverable.
- Written deliverables and exclusions
- Agreed timeline and review cycles
- Defined client inputs
- Formal completion criteria
03
Discovery & Blueprint
A structured planning engagement before a complex business, software or institutional project.
- User and requirement mapping
- Workflow and module planning
- Phased implementation roadmap
- Indicative dependencies and commercials
04
Phased Project
A larger engagement divided into approved stages, milestones and acceptance points.
- Phase-wise scope and pricing
- Milestone reviews
- Testing or acceptance records
- Controlled change management
05
Monthly Advisory
Recurring senior guidance for active business, institutional, research or digital priorities.
- Scheduled advisory reviews
- Priority decision support
- Defined document or output review
- Action notes and continuity
06
Institutional Implementation
A structured programme for multi-department software, readiness or digital-transformation projects.
- Institutional discovery
- Role and responsibility mapping
- Training and controlled rollout
- Management review and adoption support
07
Maintenance & Support
Post-launch technical continuity for approved websites, applications, plugins or platforms.
- Updates and monitoring
- Issue investigation and support
- Backup or hosting scope where agreed
- Defined service response process
08
Product Growth & Enhancement
Continuing development for a live digital platform or software product.
- Feature backlog review
- Release prioritisation
- Enhancement development
- Testing and deployment support
09
Custom Hybrid Engagement
A combined model for projects requiring consultancy, research, content, technology and continuing support.
- Multi-domain scope
- Separate workstreams
- Shared milestones and governance
- Custom commercial structure
Engagement Selection Framework
Start small when uncertainty is high; scale when the requirement is proven
The engagement should become more structured as the number of users, departments, integrations, decisions and implementation risks increase.
Idea clarity and decision urgency
Number of users and stakeholders
Expected deliverables and review cycles
Technical or regulatory complexity
Client team and execution capacity
Data, content and source readiness
Integration and third-party dependencies
Post-launch continuity requirements
Illustrative progression
Clarify
Use a strategy session when the idea, direction or professional requirement is not yet clear.
Define
Use discovery or a blueprint to convert the requirement into users, workflows and deliverables.
Build
Use a fixed or phased project to create the approved output or digital solution.
Implement
Use training, rollout and review support to move the solution into routine use.
Continue
Use advisory, maintenance or product growth for ongoing decisions and improvement.
Which Model Fits Your Stage?
Match the engagement to the decision you need to make now
A smaller engagement can be upgraded later. There is no need to commission a full project before its purpose and scope are sufficiently clear.
01
I Have an Idea but Need Direction
Begin with a Strategy Session or a short feasibility discussion.
02
I Need a Plan Before Investment
Use Discovery, Feasibility or a Business and Product Blueprint.
03
I Know the Exact Output Required
Request a Fixed-Scope Assignment with defined deliverables.
04
I Need a Complex Platform or Institutional System
Use a Phased Project or Institutional Implementation model.
05
My Project Is Live but Needs Guidance
Use Monthly Advisory or Product Growth support.
06
I Need Technical Continuity After Launch
Use a Maintenance and Support agreement.
How Scope & Commercials Are Defined
Pricing follows the actual effort, responsibility and delivery risk
01
Discovery & Planning Effort
Time required to understand the requirement, users, systems and dependencies.
02
Deliverable Volume
Number and depth of reports, documents, pages, modules, workflows or outputs.
03
Technical Complexity
User roles, integrations, data migration, automation, hosting and security needs.
04
Review & Revision Cycles
Expected approvals, stakeholder reviews and included rounds of changes.
05
Implementation Responsibility
Configuration, migration, training, launch and post-launch support requirements.
06
Timeline & Priority
Normal, accelerated or urgent delivery expectations and resource allocation.
07
Third-Party Dependencies
External services, licences, hosting, APIs, laboratories, vendors or specialists.
08
Continuity & Support
Maintenance, advisory, updates, response expectations and future development.
Engagement Process
A transparent pathway from initial discussion to delivery
The process is simplified for small assignments and expanded for complex, institutional or multi-phase projects.
01
Initial Discussion
Understand the present requirement, context, expected outcome and urgency.
02
Requirement Review
Identify users, inputs, workflows, constraints, dependencies and decision-makers.
03
Model Recommendation
Select the suitable consultation, assignment, project or continuing-support model.
04
Scope & Proposal
Confirm deliverables, timeline, commercials, responsibilities, assumptions and exclusions.
05
Delivery & Review
Complete the agreed work through reviews, milestones and acceptance points.
06
Closure or Continuity
Close the assignment or move to implementation, maintenance, advisory or enhancement.
Common Starting Options
Three practical ways to begin
Select the smallest engagement that can produce the clarity or output you genuinely need.
Early Idea
Strategy Session
Suitable for discussing an idea, comparing options, identifying risks and deciding the next professional step.
Book a Strategy SessionDefined Need
Fixed-Scope Proposal
Suitable when the required report, website, document, module or professional output is already clear.
Submit Your RequirementComplex Project
Discovery + Phased Delivery
Suitable for institutional software, multidisciplinary projects and requirements with multiple dependencies.
Discuss a Phased ProjectContinuing Need
Monthly Advisory or Support
Suitable when recurring decisions, reviews, maintenance or product improvements are required.
Working Responsibilities
Clear ownership is essential in every engagement model
Ayurvite’s Role May Include
- Review the requirement and recommend a suitable engagement model
- Prepare the written scope, deliverables, assumptions and exclusions
- Provide the agreed consultancy, research, content or development work
- Maintain communication through the approved project channels
- Raise dependencies, risks and required decisions promptly
- Complete agreed reviews, revisions and milestone records
- Protect confidential information under the applicable terms
- Recommend closure, support or a subsequent phase when appropriate
Client’s Role
- Nominate an authorised coordinator and decision-maker
- Provide accurate information, source material and system access on time
- Review and approve scope, designs, documents and decisions promptly
- Consolidate stakeholder feedback before sharing revisions
- Complete internal, legal, clinical, financial and regulatory approvals
- Manage third-party vendors and dependencies not included in the scope
- Pay approved fees and third-party costs according to the agreed schedule
- Retain responsibility for implementation, operations and compliance
Frequently Asked Questions
Before selecting an engagement model
The appropriate model depends on how clearly the requirement is defined, how many people are involved and how much implementation responsibility is expected.
Which engagement should I choose when my idea is not fully developed?
Begin with a Strategy Session, feasibility review or Discovery engagement. The purpose is to clarify the problem, users, alternatives, risks and suitable next step before a larger commitment.
Can a strategy session be converted into a project?
Yes. When the requirement becomes clear, a separate fixed-scope or phased proposal can be prepared. The session fee and project fee remain governed by their respective terms.
When is fixed-scope pricing appropriate?
Fixed-scope pricing is appropriate when deliverables, inputs, review cycles, dependencies and completion criteria can be defined with reasonable certainty.
Why are large software and institutional projects divided into phases?
Phasing reduces financial and implementation risk, allows early testing, controls scope and enables the institution to prioritise essential modules before expansion.
Can consultancy, research and software development be combined?
Yes. A custom hybrid engagement can connect strategy, documentation, research, content and technology while keeping each workstream and commercial component clearly defined.
Are revisions unlimited?
No. Included revisions are stated in the proposal. New requirements, changed decisions or work outside the approved scope are handled through a change request or separate quotation.
Are third-party expenses included in project fees?
Only when explicitly stated. Hosting, paid software, APIs, travel, printing, laboratories, specialist professionals and other external costs may be billed separately.
Can the engagement be extended after completion?
Yes. A completed assignment may move into another phase, monthly advisory, maintenance or product-growth support through a new or revised agreement.
Not sure how your requirement should be structured?
Share the present stage, expected outcome, available inputs, timeline and internal team capacity. Ayurvite will recommend the most suitable starting engagement.