How we deliver
The Answers to Your RFP's Methodology Questions
Principles, phases, and governance, written down before you ask.
Principles
Four Things We Do on Every Project
Configure before we customize
Standard objects and Flow first; custom code only when nothing standard fits.
Knowledge transfer is a deliverable
Your admins can run what we build.
Go-live is a decision
We launch when acceptance criteria are met, not on a calendar date.
The same people throughout
From scope to support, no handoff to a junior team.
The engagement
Five Stages
Discovery
Ending in written design sign-off.
Build
Two-week sprints, each ending in a demo.
Testing
User acceptance testing with your staff on real scenarios.
Go-live
Hypercare with clear exit criteria.
Support
Through an optional retainer.
Governance
A Hybrid Project Model
Predictive governance with phased delivery. Change requests go through a written form and a steering committee. Training is train-the-trainer, recorded with Scribe and Loom.
Shape
Fixed-scope accelerators
Shape
Phased projects
Shape
Staff augmentation
Shape
Ongoing support
Further reading
Guides and Articles on This Topic
Read
Standard Objects First: What We Refuse to Customize in Education Cloud
ReadRead
Flow First: How We Automate Enrollment From Checkout Without Writing Apex
ReadRead
UAT and Go-Live for a University Storefront: The Checklist We Run
ReadRead
Data Migration Into Education Cloud: A Checklist From Our Cutovers
ReadHave an RFP Open?
Send it over. We answer methodology, staffing, and references in plain language.