How We Work
Most system projects go wrong in the gaps between what was agreed, what was built, and what people actually use. The sequence below exists to close those gaps, so nothing gets decided twice and nothing gets discovered too late.
Every phase ends with something you can see and sign off, and you always know what the next phase costs before it starts.
Talk to usFive phases, in order
Each one ends with something concrete you can look at and sign off, so the project never depends on trust alone.
Planning and Discovery
We start with the business, not the software. Interviews with the people who do the work, a map of the process as it actually runs, and agreement on what success looks like in numbers. Requirements are written down and prioritised together, so the scope is a shared decision rather than something you find out about later.
- Documented process map
- Prioritised requirements
- Costed, phased plan
Design and Development
Configuration first, custom code only where configuration genuinely cannot do the job. We build in short cycles and show you working software as it lands, so feedback arrives while it is still cheap to act on. Integrations with the systems you already run, and data migration, are designed in this phase rather than bolted on at the end.
- Configured Salesforce org
- Integrations and data mapping
- Regular working demos
Testing and Deployment
Your team tests against the processes we mapped in phase one, using their own data, so the questions raised are the real ones. We fix what testing finds, agree the go-live criteria in advance, and deploy to a plan that includes what happens if something needs to be reversed.
- User acceptance testing signed off
- Migrated, reconciled data
- Go-live plan and rollback
User Training
Training is built around each role, since what a seller needs to know is not what a manager or an administrator needs to know. Sessions use your configuration and your language, not generic Salesforce demos, and your admins are taught to make changes themselves so you are not dependent on us for routine work.
- Role-based training sessions
- Documentation your team keeps
- Admins able to make changes
After Go-Live
The first weeks after launch are when adoption is decided, so we stay close: thirty days of aftercare as standard, then retained support if you want a named consultant who already knows the org. Enhancements are prioritised against what the business needs next, and Salesforce releases are tested rather than discovered.
- 30 days aftercare
- Prioritised enhancement backlog
- Release readiness
Talk Through Your Challenge
A short, pressure-free conversation to understand your context and see if we can genuinely help.
What happens next?
- We’ll reach out within one business day
- A brief call to understand your situation
- Honest advice on whether CGC is right for you
Prefer email?