AI & Digital Product Strategy
Decide what to build before you pay to build it
Get a scoped first release, an honest view of where AI helps, and a phased roadmap, before development money is committed.
Planning a new product without a live website? Contact John directly. The Audit is for established businesses with a live site.
Solution
Most product risk is created before anyone writes code
Expensive failures are rarely technical. They usually start with a scope nobody wrote down, a feature list copied from competitors, or an AI feature added because it was expected rather than because it saves real work.
By the time that shows up, the build has already formed around it, and fixing it can mean rebuilding.
Shortcut
Settle the big decisions on paper first
JMG Group works through who the product serves, what it has to do at launch, what can wait, and whether the numbers work. That covers build effort, running costs, the information the product depends on, and the revenue that has to support it.
Sometimes the right answer is to leave AI out. That is a useful outcome too.
Outcome
A first release you can build, budget and explain
Your developers, investors or team get a plan each phase can build on, so phase two extends phase one instead of replacing it.
What you receive
Five practical outputs
A scoped first release
What launches, who uses it, and what deliberately waits.
Feasibility findings
Effort, running costs, data needs and commercial fit.
An AI recommendation
Where a model earns its place, where simple automation is enough, and where neither belongs.
Major dependencies
Other systems, accounts, content or approvals the product relies on.
A phased roadmap
Each phase ships something people can use.
Illustrative example — not a client result
Reviewed drafts before automatic replies
A service business wants AI to answer customer enquiries automatically. Planning shows the replies depend on pricing and availability that change weekly.
The first release instead drafts each reply for a staff member to review and send. That saves typing time without risking a wrong promise. Fully automatic replies wait until the drafts prove accurate.
Who it suits
Products worth planning carefully
Founders scoping a first platform
Businesses replacing manual internal processes
Associations and niche industries with a defensible market
Teams with a stalled or over-scoped build
How this differs from the Direction Briefing
A deeper, separately scoped engagement
The Direction Briefing is a single decision session for an established business after its Audit. A product strategy engagement goes deeper. It is separately scoped and produces the written scope, feasibility findings and roadmap above.
How it works
Discover, define, assess, sequence
01
Discover
The business, the users, the current process and the real constraints.
02
Define
The scope, who does what, and the launch boundary.
03
Assess
Feasibility, AI fit and running cost.
04
Sequence
A phased roadmap.
From John
AI & Digital Product Strategy
I start with the business problem, not the technology.
The useful question is whether there is a repeated decision, a language-heavy task, a retrieval problem, or a workflow where a model can make the outcome measurably better. If there is not, adding AI usually creates complexity without creating much value — more moving parts to maintain, and no clearer result for the people doing the work.
AI belongs in the solution only when it earns its place.

FAQ
Frequently Asked Questions
- Do I need a website to start?
- No. If you are planning a new product, contact John directly. The Audit is designed for businesses that already have a live website.
- Will you recommend AI even if it isn't needed?
- No. If a task is better handled by simple automation, or by a person, I'll say so.
- Is the strategy tied to JMG Group doing the build?
- No. The scope and roadmap are written so any capable team can build from them.
- How long does it take?
- It depends on the product's complexity. The timeline is agreed when the engagement is scoped.
Further connections
Further connections
Have a product idea you want to test before you build it?
Tell me what you're planning. We'll start with the business problem, then decide what the first release should be.
