Implementation
Goal: Successful go-live and happy customer.
Overview
Implementation starts after the contract is signed. The goal is to get the customer generating valuable content quickly.
Implementation Checklist
1. Kickoff Call
Who attends:
- Customer: Project lead, creative/marketing team members who'll use the platform
- Dreamshot: Customer Success Manager, Account Executive (optional)
Agenda:
- Introduce the team
- Confirm project goals and success metrics
- Review timeline and milestones
- Collect brand assets and guidelines
- Schedule training sessions
Outputs:
- Implementation timeline document
- List of required brand assets
- Training schedule
2. Platform Setup
Account configuration:
- Create customer workspace
- Set up user accounts
- Configure API access (if applicable)
Brand training:
- Collect brand guidelines
- Gather product photography samples
- Train AI model on brand aesthetic
- Validate output quality with customer
3. Training
Session 1: Platform Basics (1 hour)
- Login and navigation
- Uploading product images
- Generating variations
- Downloading and exporting
Session 2: Advanced Features (1 hour)
- Batch processing
- Brand guidelines configuration
- API integration (if applicable)
- Workflow optimization
Materials to provide:
- Platform documentation
- Video tutorials
- Quick-reference guides
- Support contact information
4. First Generation
Pilot run:
- Customer uploads 5-10 products
- Generate variations with brand training
- Customer reviews and provides feedback
- Iterate on model if needed
Quality check:
- Verify brand consistency
- Confirm technical requirements (resolution, format)
- Test export to customer's channels
5. Go-Live
Launch checklist:
- Customer team trained and confident
- Brand model validated
- Integration tested (if applicable)
- Support channels communicated
Announcement:
- Internal stakeholder notification
- Optional: Joint press release or case study
6. Ongoing Review
30-day check-in:
- Usage review
- Issue resolution
- Feature requests
- Success metric tracking
Quarterly business review:
- ROI analysis
- Usage trends
- Expansion opportunities
- Renewal discussion (if approaching)
Implementation Timeline
Typical implementation takes 2-4 weeks:
| Week | Activities |
|---|---|
| 1 | Kickoff call, collect assets, account setup |
| 2 | Brand training, model validation |
| 3 | Training sessions, pilot generation |
| 4 | Go-live, first production run |
Factors that extend timeline:
- Complex brand guidelines
- Multiple brand/product lines
- Custom API integration
- Large stakeholder group
Success Metrics to Track
During implementation, establish baseline metrics:
| Metric | How to Measure |
|---|---|
| Time to first generation | Days from kickoff to first usable output |
| Volume generated | Images generated per week/month |
| Cost savings | Current photoshoot cost vs. Dreamshot cost |
| Time savings | Current production time vs. new time |
| Quality acceptance rate | % of generated images approved for use |
Common Implementation Issues
| Issue | Solution |
|---|---|
| Low user adoption | Schedule additional training, identify champion |
| Quality not meeting expectations | Review brand training, iterate on model |
| Integration delays | Involve technical team earlier |
| Stakeholder misalignment | Escalate to project sponsor |
Handoff to Customer Success
After go-live, the Customer Success Manager takes over:
Handoff includes:
- Complete implementation documentation
- Customer contact list
- Success metrics baseline
- Any open issues or requests
- Renewal date and expansion opportunities
Related Procedures
For detailed information on:
- Platform access provisioning: See
GP-011 Provision of Service - Customer support: See
GP-014 Feedback and Complaints - Design changes from customer requests: See
GP-012 Design, Redesign and Development
Signature meaning
The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:
- Author: Team members involved
- Reviewer: JD-003, JD-004
- Approver: JD-001