System and implementation
- System wireframes
- Functional requirements
- User flows
- Component library
- Technical requirements
- Frontend implementation
- Backend development
- Integrations
- Responsive implementation
- QA and testing
Investment at a glance.
Scope by phase.
Each phase is independently scoped and priced. Open a phase only when milestone-level detail is needed.
UX/UI Design Collaboration.
The Client will engage a third-party UX/UI designer to produce the final interface designs for PRISM.AI.
AXIS will provide the system wireframes, functional requirements, user flows, component library and technical requirements needed to complete the interface designs.
Final interface design
- Final UX/UI visual design
- Page and interface designs
- Visual application of the supplied component system
- Design delivery based on AXIS wireframes and functional requirements
Expected design turnaround1 week
Timeline recomputation thresholdBeyond 2 weeks
Development work that depends on final interface designs will follow the designer’s delivery schedule. If required design work extends beyond two weeks, the affected project timeline will be recomputed using the actual design delivery date, development sequencing, resource availability and resulting implementation impact. A third-party design delay is not an AXIS-controlled delay.
One acceptance rule, from build to invoice.
Staging
The intended workflow completes end to end in staging.
Regression
Existing functionality remains operational after the change.
Production
The production workflow completes without a critical blocking defect.
Build
AXIS completes the milestone.
Internal QA
AXIS validates the work and prepares a QA report.
Client Validation
You receive the acceptance checklist and supporting evidence.
Acceptance
You accept, or identify a specific failed criterion.
Invoice
Once accepted or deemed accepted, AXIS issues the invoice.
Third-party approvals, outages and processing delays do not by themselves fail a milestone when the work within AXIS control is complete and documented.
Commercial boundary.
Cost is released milestone by milestone.
Later phases proceed only after the current phase is validated.
Accepted milestones remain earned if later work changes or pauses.
If an invoice remains unpaid 3 business days after its due date, AXIS may issue written notice and pause subsequent work until payment is received. follows the agreement.
Post-project service
AXIS Maintenance & Support
Ongoing technical maintenance and support to keep PRISM stable, secure, and operational after the included project support period ends.
10%
of eligible monthly salon subscription revenue
Up to $1,000 USD / month
$100 per engineering hour · Maximum 10 hours / month
What’s Included
- Engineering hours based on the monthly maintenance allocation, up to 10 hours per month
- Bug fixes and troubleshooting
- Routine platform maintenance
- Dependency and security updates
- Minor third-party API and integration adjustments
- Deployment and production support
- Technical monitoring and issue investigation
- Minor configuration and technical adjustments
- Priority 1 response within 4 business hours during the standard support window
- 24/7 escalation path for urgent P1 support
Engineering Hours
Included engineering capacity is calculated using the applicable monthly maintenance allocation at $100 per engineering hour.
For example, a $599 monthly maintenance allocation provides 5.99 included engineering hours.
The standard maintenance allocation is capped at $1,000 per month, providing a maximum of 10 included engineering hours.
Engineering time is deducted as maintenance and support work is performed. Unused engineering hours do not roll over to future months.
$2992.99 hours
$5995.99 hours
$8008 hours
$1,00010 hours maximum
Eligible revenue means recurring PRISM.AI salon package fees collected during the applicable month. It excludes taxes, refunds, credits, chargebacks, onboarding and one-time fees, usage overages, third-party provider charges and pass-through expenses.
Scope Boundaries
Quoted separately before development begins:
- New features or modules
- Major feature enhancements
- New CRM or third-party integrations
- Major redesigns or workflow changes
- Work requiring substantial new development
- Third-party provider fees
- Infrastructure costs
- AI usage
- Telecom and messaging costs
- Other PRISM operating costs
Any work outside the existing platform maintenance scope is reviewed and quoted separately before development begins.
Maintenance begins after the applicable included project support period. PRISM operating costs and third-party provider charges remain separate from the AXIS maintenance allocation.