Less repetitive work
Give routine tasks a clear path, so people can focus where they add value.
Product thinking. Practical technology.
I help businesses turn complex challenges into better products, smarter workflows and practical AI applications. From figuring out what to build to making it work.
Alex Mackay’s independent product & technology practice.

The business goal, the people involved and the constraints that matter.
Product decisions, journeys and interfaces that make the idea tangible.
The right tools, information and controls, working together.
A useful release, tested with people and improved through use.
Some problems need a better product. Others need a clearer process, more useful information or carefully applied AI. Understand the problem before choosing the technology.
An opportunity, a difficult product decision or an idea that needs a clearer shape.
A direction worth building towards.Explore this workRepetitive work, scattered knowledge or a process that could work better with the right support.
Useful systems, with the right controls.Explore this workA promising concept or prototype that needs to become something people can use.
A working solution, grounded in reality.Explore this workWhat changes when the right technology meets the right problem? Less time reassembling the context. More attention on the work that matters.
The work moves, but the context keeps getting lost.
Useful information exists. Reassembling it becomes a job of its own.
People spend their attention on the parts that need judgement.
Clearer software first. Automation where the rules are known. AI where interpretation helps.
Illustrative workflow. The right solution depends on the process; it may not need AI at all.
Get close to the problem, make the idea tangible and learn as it develops. Select a stage to explore the questions and the work.
Find the real problem.
What is getting in the way, for whom, and why does it matter?
A shared problem definition and a view of the constraints.
Choose a useful direction.
Which assumptions need testing? What belongs in the first version?
A clear proposition, prioritised scope and a prototype to learn from.
Make the idea tangible.
Does it work for the people using it? Where does it break?
A working prototype, feedback and decisions about what to change.
Fit it into the real world.
How will data, tools, access and day-to-day ownership work together?
A usable release, appropriate checks and a practical handover.
Learn from actual use.
What is helping? What needs adjusting? What is worth doing next?
A feedback loop and a focused next set of improvements.
Learn, revisit, refine. A working approach, not a one-way process.
Useful AI connects the task, the right information and permitted tools, with a person in control of important decisions.
“Prepare me for tomorrow’s customer meeting.”
Illustrative example“Here’s a suggested agenda and a few preparation tips.”
Useful advice. You still find the information.The brief is prepared from the context you’ve permitted it to use.
Select a step to see the work behind it.Find tomorrow’s customer meeting in the calendar you have allowed the system to read.
Attendees identified from the invitation. If there are two plausible meetings, ask which one.
Retrieve relevant records, recent exchanges and documents within the user’s permissions.
Current objectives, the last conversation and open actions. Missing or conflicting records stay visible.
Look for relevant company developments. Keep sources attached and distinguish evidence from interpretation.
Recent updates sit beside their source links. Uncertain matches are flagged rather than treated as facts.
Assemble a concise briefing around the purpose of the meeting, with open questions and gaps.
Account summary · previous commitments · suggested discussion points · questions to clarify.
Check the evidence, correct the gaps and decide what to use. Nothing is emailed or committed on your behalf.
The system gathers and prepares. You decide what matters, what is correct and what happens next.
A design illustration, not a client delivery or a live integration. No tools are connected and no data is sent.
The point is a useful change in how the business works. Start with what better should look like, then design and test towards it.
Give routine tasks a clear path, so people can focus where they add value.
Bring the relevant context into the moment someone needs it.
Test important assumptions before committing to a bigger build.
Make evidence, trade-offs and uncertainty easier to see.
Connect the hand-offs instead of adding another isolated tool.
Design around the customers and teams doing the work.
Actual products, the decisions behind them and my contribution.

From a will-writing proposition to an employee education platform and an AI-assisted publishing workflow.
£1.2m qualified pipeline through the accompanying GTM system. Pipeline, not booked revenue.

Product direction and experience design for connected client information, documents and adviser casework.
A clearer relationship between the client context, the next action and adviser review.
One complicated idea. A clearer way to think about it.
How the pieces fit together, what’s genuinely new, and what it means for your work and your day.
Read the guide
Alex Mackay · Founder, revarc
My background spans security engineering, enterprise software, BCG Platinion consulting and product marketing. Today, I bring those perspectives together to shape products, design useful systems and drive implementation.
More about meWhether you’re exploring an idea, improving a process or figuring out where AI fits, I’d be happy to talk.