What is an AI Implementation Sprint?
A productised build that implements one named AI workflow in production, integrated with your existing stack, with weekly demo cadence and 30 days of stabilisation. Built on whichever tool genuinely fits the job: Make.com for orchestration-shaped workflows, or bespoke code via Claude Code where the build is genuinely a custom application or dashboard. Two delivery shapes: Quick Win (£1,500 to £3,500, 1 to 3 days) for small, tightly-scoped automations; Standard Sprint (from £8,000, 4 weeks) for production workflows. The Sprint is Step 03 of the Wingenious approach, typically scoped from a prior Readiness Audit, sometimes after a £1,000 Prototype.
Why two delivery tools: Make.com or bespoke code?
Right tool for the right task. Make.com suits a wide app library and managed infrastructure for orchestration-shaped builds, and is fast for a non-technical SME team to maintain. Bespoke code via Claude Code suits genuinely custom applications, internal dashboards, or LLM-powered tools that no off-the-shelf workflow platform handles cleanly. The audit recommends which tool for your specific build; we are not loyal to any platform. For some Sprints we use a combination (Make.com orchestration plus a small bespoke component, for instance).
How is a Quick Win different from a full Sprint?
Scope and shape. A Quick Win is a single, tightly-defined automation that takes one to three days of senior time to implement, typically £1,500 to £3,500. Examples: an automated invoice email-extraction flow, a single-purpose Slack bot, a Klaviyo flow rebuild, a custom Zapier replacement that broke. A Standard Sprint is a four-week production workflow with integrations, monitoring, documentation, training, and a 30-day stabilisation tail. The audit ranks candidate builds against this shape; some are Quick Wins, some are Sprints, the framework picks the right one.
Is £8,000 really fixed, or is that the starting price?
It is the starting price for a Production Sprint, the largest of the three shapes: a four-week production workflow with multi-system integration, monitoring, documentation, training and a 30-day stabilisation tail. If your build is smaller than that, the right shape is either a Focused Sprint (£4,500 to £7,500, 1 to 2 weeks, one workflow with light integration) or a Quick Win (£1,500 to £3,500, 1 to 3 days, single tightly-scoped automation). If none of those shapes fits your scenario, we scope to value and quote fixed-price after a 30-minute discovery call. No time-and-materials, no scope creep, always a fixed quote up front. The Feasibility Study (£3,950) covers detailed scoping where the workflow needs proper analysis before quoting.
Do you build AI Implementation Sprints for our existing stack?
Yes. That is the default. We integrate AI on top of whatever stack you already run. Common integrations: Shopify, WooCommerce, Magento, BigCommerce (ecommerce); Salesforce, HubSpot, Pipedrive, Close, Attio (CRM); Xero, QuickBooks, Sage (accounting); SAP, NetSuite, Epicor (ERP); Gorgias, Zendesk, Intercom, Tidio (support); Klaviyo, Mailchimp, ActiveCampaign (marketing). For unusual stacks we add an integration assessment to the Feasibility Study.
What kinds of workflows can be built in a Sprint?
The spokes under this pillar cover the typical shapes: workflow automation, document management, customer support, lead generation, personalised recommendations, customer segmentation, pricing optimisation, data cleaning, actionable dashboards, multilingual customer support, marketing automation, CRM automation, HR/recruitment automation. Anything we can scope clearly + implement in 4 weeks fits the Sprint shape. Larger initiatives (multi-month builds, novel R&D) are scoped as multiple Sprints or as Fractional CAIO engagements.
Can we test before committing £8,000?
Yes. The £1,000 / 7-day Prototype Guarantee is designed exactly for this. We build a working prototype of the proposed Sprint workflow for £1,000 in seven days. If you proceed to the full Sprint within 60 days, the £1,000 credits in full. If you walk away, you keep the prototype. The lowest-risk path to commit to a Sprint.
What does "30-day stabilisation" actually mean?
After the Sprint goes live, the workflow runs in production for 30 days under our oversight. We monitor performance, fix issues, tune accuracy, support your team using it. After 30 days the workflow is fully owned by you. You can run it indefinitely without further Wingenious involvement, or move into Fractional CAIO for ongoing optimisation. The 30-day window is fixed; no surprise post-go-live invoicing.