Design & build | Alan Lindsay Consulting

Design with AI

Interfaces for complex, high-stakes work, including the AI inside them.

I design for places where a confusing screen has a real cost: fraud investigation, identity checks, enrollment at scale. The work covers research, information hierarchy, and engineering-ready designs that account for the edge cases.

AI is showing up on more of those screens. It drafts, suggests, and sometimes acts on its own, and people still have to trust it, check it, and overrule it. I design that working relationship as carefully as the rest of the interface, and I use AI in my own process to explore more directions in the same time.

Where many teams share one product surface, I build the design system that keeps them consistent.

Engagements are scoped as statements of work.

I’ve worked with Alan at four companies. He has a sharp sense of where design effort matters most, for internal teams and external users alike.

Jaime E. Soto, PMPPrincipal Owner, Andes Consulting · Via e.Republic, Builderhub, and OneShare Health

On the menu

Ask about design with AI

AI interaction designDesign how people work alongside AI: what it suggests, what it does on its own, and how people check and undo it.
Design workshopsBring product, engineering, and stakeholders to a shared direction.
User researchUnderstand where people struggle and what they need to succeed.
Information architectureOrganize the product around the decisions people need to make.
Interface designCreate interfaces that hold up in real use, edge cases included.
PrototypingExplore more directions quickly, with AI where it helps, and learn what works before investing in a build.
Design systemsKeep many teams building one consistent product.
UX reviewKnow what is holding a product back and what to fix first.

You might need this if…

A confusing screen costs you missed cases, bad decisions, or support tickets.
An AI feature works in the demo, and people do not trust it in real use.
Several teams build on one product and it no longer looks like one product.

Selected examples

Experian. Led the global design system across more than 40 product teams and 70 applications, and designed fraud and identity tools whose decision-first layout roughly tripled case throughput.
He led the creation of the fraud and identity design system, partnering with engineers on usable component libraries.
Matthew SolisSenior Product Designer, Google Workspace · Via Experian
Circadence. Redesigned the cybersecurity training experience from scratch.
The 41st Parameter. Engineered the frontend of a high-volume fraud and identity platform, partnering with risk specialists so the fraud logic stayed accurate on screen and dashboards over datasets of 100,000 records stayed responsive for analysts.
Alan strives for holistic approaches in requirements, design, execution, and delivery, always with the users in mind.
Ries van ZoestData science and risk management · Via The 41st Parameter and Experian
OneShare Health. Overhauled the enrollment, producer, and internal tools so throughput grew without adding support staff.
OneShare Health. Designed the AI ticket writer and AI report generator as well as building them: the AI drafts, and a person reviews and approves before anything goes out.
Alan Lindsay Consulting. Designed how people direct and review AI agents in the systems this practice runs on: where direction is captured, what each agent is shown, and where a person signs off on the result.

Development with AI

A scoped build, AI features included, delivered to production and handed over.

When the recommendation is to build, I build it: architecture, implementation, and the hardening that gets it into production.

That increasingly means AI in the product: features that draft, summarize, or classify, and connections that let your customers’ own AI assistants work with your system. I build those on fixed steps with checks, so the output holds up on real cases and not just in a demo.

I also build with AI every day. It widens what one person can deliver in a scope, and the architecture, review, and handover stay with me. Each build is its own statement of work with a defined scope and a handover at the end.

Engagements are scoped as statements of work.

Always patient and measured, with deep technical knowledge he was able to impart very effectively.

Matt CalthropFull-stack engineer · Via Experian

On the menu

Ask about development with AI

AI features and agent accessBuild the AI features and agent connections the recommendation calls for, with checks for when the AI is wrong.
ArchitectureBuild on a foundation sized to the scope and the team that will own it.
Frontend engineeringDeliver fast, accessible interfaces that stay responsive at scale.
Pipelines and integrationsKeep data flowing reliably between the systems the business runs on.
Data model and migrationPut the data on solid ground, including a safe move off legacy platforms.
Production hardeningTurn something that works into something the business can rely on every day.
HandoverLeave the team confident owning, changing, and extending what was built.

You might need this if…

A recommendation calls for a build and no team is free to take it on.
An AI prototype works in a demo and has never been hardened for production.
A manual, paper-based process costs more every year it stays that way.

Selected examples

OneShare Health. Built an AI ticket writer and an AI report generator into the company’s internal platform, integrated with its ticket system and used daily in operations.
Alan Lindsay Consulting. Designed, built, and run daily the systems this practice works on: a work tracker that AI agents connect to through an authenticated API to take on and resolve work, and pipelines that keep each AI step on fixed rails.
OneShare Health. Designed and built an omni-channel enrollment pipeline from scratch across three channels, including the data model, the migration, and future-dated enrollments, so the service runs around the clock.
Experian. Built the design system as shipped code, not just design: coded components delivered to product engineers and maintained alongside the engineering teams that used them.
The 41st Parameter. Designed and built three separate product interfaces, owning the frontend architecture and code as well as the user experience.
Patterson Homes. Built a document processing pipeline for a largely paper-based home builder that dramatically simplified and accelerated management of subcontractors and home buyers.
e.Republic. Worked closely with the CIO to bring development in-house and build a publishing platform for the company’s writers, leading a team of six programmers.