STQRY

Discovery & scoping (2–6 weeks)

• Goals: Define objectives (e.g., tours, stories, wayfinding), audience, devices (mobile, tablet, kiosk), and accessibility needs.

• Content audit: Inventory media assets (images, video, audio), metadata, geospatial data, and storytelling structure.

• Success metrics: Engagement goals, completion rates, shareability.

Information architecture & design (2–4 weeks)

• Storyboards: Map the narrative flow, chapters, and sequencing.

• Map design: Decide basemaps, markers, clustering, filtering, and search behavior.

• UX requirements: Offline support, multilingual support, accessibility ( WCAG ), and responsive layouts.

Content ingestion & preparation (2–6 weeks, parallel with design)

• Data import: Upload places, routes, stories, multimedia assets, and metadata.

• Validation: Ensure geolocations, timestamps, and relationships are correct.

• Media optimization: Transcoding, compression, captions, alt text.

Development & customization (2–8 weeks)

• Template configuration: Adjust STQRY templates (themes, layouts, interactions).

• Custom features: Integrations (CMS, CRM, ticketing, analytics), custom widgets, or APIs if available.

• Branding & localization: Colors, fonts, language variants, right-to-left support if needed.

Testing & QA (1–3 weeks)

• Functional testing across devices and browsers.

• Performance tests for large tours or datasets.

• Accessibility and localization checks.

Deployment & rollout (1–4 weeks)

• Environment setup: Production vs. staging, user roles, permissions.

• Data migration: Cutover from legacy systems if applicable.

• Training: Admins and editors training, content editors onboarding.

Content customization

• Full control over story structure, chapters, media timelines, hotspots, and interactions.

• Support for rich media (images, video, audio), captions, metadata, and searchability.

• Multilingual content and localization workflows.

Map & interaction customization

• Custom basemaps or branding overlays.

• Custom filters, search facets, and guided tours.

• Route planning, waypoint sequencing, and milestone triggers.

Integrations

• CMS integration for content workflows (e.g., DAM, headless CMS).

• Analytics integrations (Google Analytics,/or platform-specific analytics).

• CRM or marketing automation integrations for lead capture or user management (if supported).

Setup/configuration/setup fees

• Initial project scoping, onboarding, and environment setup (often a one-time cost or rolled into an implementation package).

Licensing & subscription

• Annual or monthly fees based on users, projects, or data volume.

• Tiered pricing for features, such as advanced analytics, enterprise security, or SLA levels.

Content migration & ingestion

• Costs for migrating existing content, media encoding, metadata tagging, and dataset normalization (if applicable).

Custom development and integrations

• Fees for bespoke features, API integrations, or custom widgets beyond standard templates.

Training & enablement

• Admin/editor training sessions, documentation, and ongoing support materials.

Maintenance & support

• Ongoing: technical support, bug fixes, platform updates.

• SLA-based support (response times, uptime commitments).

Hosting & infrastructure

• If not fully SaaS, costs for hosting, CDNs, data egress, or disaster recovery.

Localization & translations

• Costs for professional translation and localization workflows.

Admin/Editor onboarding sessions: Structured sessions to set up environments, roles, permissions, and editorial workflows.

Hands-on workshops: Guided exercises to build a first project, ingest media, create stories, and publish.

Self-paced documentation: Comprehensive guides, tutorials, and best-practice checklists

Video tutorials: Short how-to videos covering common tasks (content ingestion, map configuration, publishing workflows).

Webinars and Q&A sessions: Regular live sessions on new features, use cases, and troubleshooting.

Role-based training: Tailored tracks for admins, content editors, designers, and developers (if integrations are involved).

Localization/Accessibility training: Guidance on multilingual content workflows and WCAG-compliant design where applicable.

Access control: Role-based access control (RBAC) with granular permissions, least-privilege access, and multi-user collaboration controls.

Authentication: Support for SSO (SAML/OIDC), and strong password policies; session management and token-based authentication for APIs.

Data encryption:

• In transit: TLS/HTTPS for all data transfers.

• At rest: Encryption for stored assets and databases (AES-256 or equivalent).

Data residency options: Regional data storage choices where available; options for data localization in certain regions.

Regular release cadence: Many SaaS platforms publish updates quarterly or biweekly with minor patches as needed.

Major vs. minor releases:

• Major: new features, architectural changes, potential UI/UX overhauls.

• Minor/patch: bug fixes, security patches, small enhancements.

Automation and CI/CD: Deployments typically happen through controlled pipelines with staged environments (development, staging, production).

Release notes: Detailed documentation of changes, new features, deprecations, and migration steps.

Backward compatibility: Efforts to minimize breaking changes; deprecation notices and sunset timelines when necessary.

Testing and QA: Pre-release testing, including compatibility tests for existing projects, before pushing to production.

Migration assistance: Guidance or tooling for migrations when schema or workflow changes are required.

Upgrade assistance: Support for plan/feature upgrades; sometimes optional professional services for complex transitions.

Scaling model

• Clear pricing and provisioning model for scaling users, projects, storage, and API calls.

• Elastic scalability for concurrent users and peak loads, with defined upper bounds or auto-scaling behavior.

Upgrade/downgrade paths

• Seamless plan changes with proration or true-up considerations at renewal dates.

• Migration assistance for moving to higher tiers or rolling back features if needed.

Exit ramp when scaling down

• How to decommission projects or reduce licenses while preserving data export rights.

• Potential penalties or fees for early termination of contracts tied to committed volumes.

Performance guarantees

• SLA for performance metrics (latency, uptime) that may scale with usage levels.

• Capacity planning guidance or dashboards to monitor usage trends.

Scaling model

• Clear pricing and provisioning model for scaling users, projects, storage, and API calls.

• Elastic scalability for concurrent users and peak loads, with defined upper bounds or auto-scaling behavior.

Upgrade/downgrade paths

• Seamless plan changes with proration or true-up considerations at renewal dates.

• Migration assistance for moving to higher tiers or rolling back features if needed

Exit ramp when scaling down

• How to decommission projects or reduce licenses while preserving data export rights.

• Potential penalties or fees for early termination of contracts tied to committed volumes.

Performance guarantees

• SLA for performance metrics (latency, uptime) that may scale with usage levels.

• Capacity planning guidance or dashboards to monitor usage trends.

General data protection and privacy

• GDPR readiness (data processing agreements, DPA, data subject rights handling).

• CCPA/CPRA considerations if handling California resident data.

• data residency options and cross-border data transfer safeguards.

Security certifications and frameworks

• ISO 27001 or equivalent information security management system.

• SOC 2 Type II or SOC 1/2 reports availability.

• SOC 2 type II or ISO 27001 attestation accessible to customers via auditor package.

• PCI DSS, if processing payment data (likely not for this type of product, but confirm if payments are involved).

Access and identity governance

• Support for SSO (SAML/OIDC), MFA, RBAC, and granular permissions as part of security controls.

Data protection measures

• Encryption in transit (TLS 1.2+), at rest (AES-256 or equivalent).

• Key management approach (customer-managed keys vs. vendor-managed keys).