Component Add-On Sprint
Timeline: 2-3 working days
Investment: From £1,500 + VAT
Prerequisite: Requires existing Rivetous Foundation
Add more components to your Foundation from our catalog. Each sprint adds 3-5 additional components, fully documented in your existing Storybook.
- What's included: Component implementation following your existing design token architecture, CVA variant definitions, full TypeScript types, and Storybook story documentation.
- What's excluded: New design tokens, fundamental style system changes, or components requiring external dependencies not already in your kit.
Component Enhancement Sprint
Timeline: 2-3 working days
Investment: From £1,200 + VAT
Prerequisite: Requires existing Rivetous Foundation
Enhance your existing components with micro-interactions, transitions, or animation behaviors. We add motion design that respects user accessibility preferences and maintains performance.
- What's included: CSS transitions, Framer Motion integration for complex animations, reduced-motion media query support, and updated Storybook stories demonstrating the enhanced states.
- What's excluded: Complex multi-step animation sequences requiring custom JavaScript choreography, 3D transforms, or scroll-triggered animations requiring external libraries.
Feature Add-On Sprint
Timeline: 1 week (5 working days)
Investment: From £3,500 + VAT
Prerequisite: Requires existing SaaS Starter
Add an additional feature module to your SaaS Starter following the established feature folder architecture. You provide an OpenAPI specification; we deliver a complete feature module with CRUD flows, data tables, forms, and validation.
- What's included: One feature module folder with list/detail views, create/edit forms, React Query hooks, MSW mock handlers, TypeScript types generated from your OpenAPI spec, and full test coverage.
- What's excluded: Complex multi-entity relationships requiring coordinated writes across multiple API endpoints, real-time WebSocket integrations, or features requiring third-party service dependencies.
Important: If you don't provide an OpenAPI specification, we will assume a reasonable API shape based on your feature requirements. Retrofitting with your actual API structure later will require an additional sprint to reconcile the differences.