Build an LMS in Power Apps with AI, and prove it works before anyone else touches it.

Your progress, private notes and saved work remain on your account. Full access to protected content in Power Apps Builders lasts for the period you choose; afterwards, protected steps require an active plan, permanent Space ownership or Team access.

Your 90-day Learning Pass starts when payment is confirmed, not when you first open a lesson or Board item.

The page checks your account and Team access before checkout. It keeps your existing Board and progress, avoids duplicate charges, and shows the right ongoing option if the one-off offer no longer applies.

AI can answer individual questions. This Board adds the chosen sequence, named outputs, progress tracking and related Space material for the context and edge cases you would otherwise have to assemble yourself.

The current estimate is 37 hours 20 minutes, completed at your own pace over Two focused days, or a week of evenings. Testing, deploying and the handover add about fifteen hours.. The complete learning path is visible on this page before you start.

No. The Board gives you a practical learning path and supporting material, but you still make the decisions and do the work. It is a product, not a done-for-you consulting service.

Because the first time you run a method is the worst possible time to run it on something people depend on. Here you can set the data row limit to 1, cut the connection mid-save and break the thing on purpose, with not one real record at risk and nobody watching. The app is the practice ground; the method is what you keep, and you can point it at the real one the following morning. The fictional data is a safety rule as much as a convenience: no real people, tenant IDs or secrets go into any AI conversation, and one step checks your app's files for hard-coded keys and names before an AI tool reads them. If what you need is an LMS installed for your organisation, this is not that.

You can, and it will hand you one by tonight. It is probably how you got here. The trouble is a one-off generation cannot be checked: every prompt produces a different app, there is no specification to test it against, and when a number looks wrong you cannot tell if the fault is the app's or yours. The Blueprint is the opposite of a prompt: fifty thousand words of fixed specification, every table, column, formula and test record decided in advance, so each step has one correct state, checked in the saved record, not the screen. The AI coaches, you perform every action, and a failed check tells you which side the fault sits on. Free gets you an app. This gets you one you can vouch for.

Two different things, and the first step checks both. For building, an ordinary ChatGPT or Codex conversation is enough: you paste the Blueprint in and it coaches you. For testing, moving and documenting you need a tool that can open files on your computer: Claude Code or Claude Cowork, OpenAI Codex, or GitHub Copilot in agent mode. Those phases ask it to read your whole app at once. The test: point your tool at any folder and ask it to list the files. If it lists them, you are set. If it asks you to paste them in, it is the wrong kind. GitHub Copilot's free tier in VS Code passes the test, so a failed test costs you a download, not a purchase.

The build is two focused days, or a week of evenings around a job. Testing adds about six hours, moving about three and a half, the handover about five. Honest figures, not brochure ones. Getting stuck is planned for, because it is where courses die. If a step leaves the app in a state the Blueprint does not recognise, the run halts rather than guess, and the recovery rules name the way back. The AI keeps a log of where you slipped and tightens its later instructions to match. You save a named version at every phase gate, so the worst case is a restore, not a rebuild. Five visible wins mark the route: each sitting ends on one, the next step written down, the Board holding your place.

You will learn the whole route and practise it end to end for free, in a second Developer environment. Whether you can then deploy to production at work is your organisation's call, not a platform rule: many organisations choose to gate production behind managed environments, and that gate carries paid licensing. No course can hand you that access, and this page will not pretend otherwise. What the Board gives you is the exact request to send your administrator, the reason it is needed, and the answer to the first question they will ask, which is whether you have tested it. You will be holding a Release Check Record that says yes, with dates.

The Board is $99. Launch week takes 30% off it, so you pay $69.30. The deadline on this page is set by the system, not by us, and it cannot be extended afterwards, which is the only reason a deadline is worth printing. There is no seat limit, because that would be theatre. What the money buys is the Board permanently, plus 90 days of the full Power Apps Builders Space, which sells on its own at $139 for permanent access. It is a one-time purchase, one pass per person; if you would rather take the membership route instead, that option sits beside it at checkout.

Three things are yours for good: the Board, your progress on it, and every private note you made along the way. So is everything you built, because the app, the tests and the Handover Pack live in your Microsoft environment, not ours. What closes is the library: the Board's protected course steps draw on the Space, so after day 90 they need an active plan or Space access to reopen. In practice the route wants thirty to forty-five focused hours and you have ninety days, so finish inside the window and you keep every artefact that matters. If you want the library open beyond that, take a plan or permanent Space access at $139.

Then you get your money back. Seven days, full refund, no questions asked. You do not need a reason, you do not need to show your work, and there is no form designed to wear you down. Email, refund, done. Seven days is enough to know: the environment check takes about a minute and the first build session takes an evening, so you will have real evidence either way well before the window closes. And since the tables you build live in your own Microsoft environment, whatever you made in that evening stays with you regardless.