KJM / THE PRACTICAL AI TOOLKIT

Put AI to work.
Keep clear boundaries.

Practical guidance from building KJM’s website, reusable controls and business tools. Understand the decisions, use the examples, and leave with something you can apply.

  • Real decisions
  • Useful working examples
  • Clear data boundaries
WHO THIS IS FOR

For people who use AI, not people who write software

This toolkit is for business people using AI to create documents, build web pages or vibe code simple tools. It shows you how to get better results while keeping the risks under control.

Professional developers will have more advanced tools and practices. Use this as a guide to the decisions, not a replacement for those.

Start with the overview below, or go straight to the practical guides and example master prompts

UNDERSTAND THE PROBLEM

AI builds apps faster than anyone can secure them

AI lets almost anyone build a polished web page or app in an afternoon. It lets attackers find the weaknesses just as quickly. The result looks finished long before it is safe.

The KJM AI Toolkit closes that gap. Instead of building your own authentication, hosting and data protection, your custom AI apps run inside the Microsoft 365 or Google Workspace security you already pay for. You get the speed of custom AI without standing up a security function to support it.

It does not replace good development practice. Used with discipline, it lets you replace selected SaaS subscriptions with apps you own and control.

EXPLORE THE APPROACH

See how the architecture works in practice

This isn't a theoretical model. It's how KJM runs today. The architecture has three layers, and each one has more access to data and tighter controls than the one before.

Public site Custom AI-built components on our website, such as our lead capture forms. They have no direct access to internal data, so a compromised page exposes nothing of value.

Secure connections Controlled links between public components and internal systems. Authentication and permissions run through Microsoft 365, not custom code, so there are no home-grown login systems to attack.

Internal apps Custom apps that work with client data, such as our CRM and KJM Flow Studio running in SharePoint. They sit entirely inside our tenant and are governed by the same identity, access and audit controls as the rest of the business.

The pattern is simple. The closer an app gets to sensitive data, the more it relies on platform security rather than its own.

The whole picture

FREE WITH OUR NEWSLETTER

Create your own interactive diagrams like this one

We built KJM Flow to make diagrams like the one above. Subscribe to our newsletter and you can use it free to map your own processes, systems and journeys.

HOW TO USE THIS TOOLKIT

Start with something you already pay for, or are about to

SaaS pricing is built to look cheap on day one. The features you'll actually need, like integration, automation and proper reporting, are always a tier or two up. When we needed a CRM, we saw that early and never signed up. We built our own on Microsoft infrastructure instead. The steps below show how, so you can do the same.

 

1. Price the tier you'll actually need

Ignore the entry price. Work out which tier covers what you'll need in twelve months, multiply by your user count and compare that with building. For an existing subscription, check what you're about to be pushed into.

Our example: lead capture, consent tracking and automation all sat in the higher tiers of every CRM we looked at.

2. Decide where the data belongs

Before any design, work out what the app holds, who needs it and how sensitive it is. Sensitivity decides location.

Our example: the CRM holds client contact and consent data, so it stays inside our tenant. The public website only passes enquiries in. It never stores them.

KJM AI Toolkit: five steps from idea to trusted app

3. Design the architecture before the AI writes code

Left alone, AI will solve the same problem three different ways. Set the rules first:

One source for master data. Statuses, categories and consent types are defined once, so the AI can't create versions that drift apart.

Modular by design. Each change touches only the module that needs it, not the whole app.

A living architecture reference. The AI maintains a map of components, files and dependencies, and reads it before every change so it knows what to update and what could break.

Our example: every CRM build session starts from the architecture reference, and all shared values come from master data.

4. Build on the platform, and plan for the last 20%

Run on infrastructure you already own and build app security on Microsoft or Google identity management, not custom logins. AI gets you to 80% fast.

The real effort is the last 20%: edge cases, permissions, error handling and the details users notice straight away. Good architecture keeps that effort focused instead of turning it into rework.

Our example: first working version in days, production-ready in weeks.

5. Pilot small, with people who want it to work

Release in small batches to users who know they're testing and will tell you what's wrong. Fix what they find, then widen the rollout. Keep the existing process as a fallback until each batch runs cleanly, and only then make the new app the system of record.

Our example: we piloted the CRM features in small batches with willing test clients. Issues were found and fixed before they reached the wider client base.

KJM Practical AI Toolkit · Edition 2 · 18 November 2026

HAVE A PERSPECTIVE

Ask questions, share your thoughts and help your community

0 comments

Ask a question, share your experience or tell us what you think of this toolkit. Your insights help others in the community. If you find it useful, please share it with your network. If not, tell us why below.

Leave a comment

Community discussion

0 contributions

No comments yet. Start the conversation.

Leave a Reply

Your email address will not be published. Required fields are marked *