A library for the people who run things.

You do not have to read this book in order, and you do not have to finish it in one week. It is arranged as a week because that is a shape people complete, and the day names are labels rather than orders. Each chapter opens with the point o

You do not have to read this book in order, and you do not have to read all of it. It is built like a field guide. Start where your worry is, and follow the cross-references when you want more. Each chapter opens with a scene, explains the

You do not have to read this book in order, and you do not have to read all of it. It is built like a field guide to a bill nobody prints. Start where your question is, and follow the cross-references when you want more. Each chapter opens

You do not have to read this book in order, and you do not have to read all of it. It is built like a field guide for a worried parent with about forty minutes. Start where your worry is. Each chapter opens with a scene, explains what is re

You do not have to read this book in order, and you do not have to read all of it. It is built like a field guide. Start where your worry is, and follow the cross-references when you want more. Each chapter opens with a scene, explains the

You do not have to read this book front to back, and you do not have to finish it in one sitting. It is built to be opened at the chapter that matches the headache you have this week. Read a little, try one thing, come back for the next. Ev

You do not have to read this book in order, and you do not have to read all of it. It is built so you can start where your worry is loudest, get a real answer, and then decide what to do next. Read it with a pen. The parts that make you say

This book is short on purpose and built to be useful at any page. Here is how the parts fit together, so you can start where your curiosity is.

This book is built to be read in order, but it will not scold you if you skip around. Each chapter opens with a real moment, explains one idea in plain words, and ends with a small thing you can try. Read with your phone or computer nearby,

This book is built for a busy life, so you can read it any way that fits your week. You can start on page one and go straight through, or you can flip to the part that matches the question keeping you up tonight. Nothing here assumes you re

You do not have to read this book in order, and you do not have to read all of it. Think of it as a toolbox. When something lands in front of you and you are not sure, open the drawer you need.

This book is built to be used, not just read. You do not need any technical background, and you do not need to finish it in one sitting. Think of it as a friend you can call when a money question or a suspicious message shows up. Each chapt

You do not need to read this book in order, and you do not need to read all of it. Start where your worry is. Each chapter opens with a real moment, explains what is happening in plain words, then hands you one small step you can take the s

This book is short on theory and long on things you can try tonight. Read it front to back, or jump straight to the chapter that matches the problem in front of you. Either way works. Here is how it is put together.

You do not need any technical background to read this book, and you do not have to read it in order. Some people want the whole story from front to back. Others just want to understand their next bill or make sense of one confusing headline

You can read this book straight through, or you can open it to the part that matches the meeting on your calendar. Each chapter opens with a real moment, explains the idea in plain words, and ends with something you can do. Nothing here ass

This is a working manual, not a book you read once and shelve. Keep it near the people who are actually using AI, and treat each chapter as a short conversation you have with your team before you turn a tool loose on real work. You can read

Read this book the way you would use a map before a long drive. Skim the whole thing once so you know what is ahead, then come back to the part that matches where you are right now.

This manual is built to be worked with a spreadsheet open beside it. Keep one folder, on paper or on screen, and put every output into it as you go. Fourteen chapters produce a small stack of short documents, and the last chapter turns them

This manual is built to be worked with a terminal open and a document beside it. Keep one folder for the outputs. Thirteen chapters produce a baseline, an audit, a budget, a tag list and a plan, and the last chapter ties them together with

This manual is meant to be worked, not admired. Read it with a notepad, a staging copy and your hosting login within reach. Almost every chapter ends with something you can finish the same day.

This is a working book. It is meant to be open beside you while you change things, not read once and shelved.

This manual is built to be worked with a spreadsheet open beside it. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single n

This manual is built to be worked, not read once. Each chapter ends with something you write down, and the next chapter asks for it. By the last page, those pieces add up to one dated plan you can pin to a wall.

Every chapter is built the same way. A real situation, then the explanation in plain words, then something you can do this week. Read it front to back the first time, or open it at the chapter that matches the fault you already know about.

This book is built to be worked, not read once and shelved. Eighteen chapters sit in five parts, and the parts run in the order you would actually do the job. Read part one first even if you are in a hurry, because it is the part that stops

This is a working manual for a store that already takes money, or is about to. Read it with your payment dashboard open on one screen and a notepad beside you. Almost every chapter ends with something you can set up, test or verify the same

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce eight documents, and the last chapter turns them into a single plan with date

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into six templates and a

This manual is written to be worked, not read once. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single calendar and a dat

This is a worklist with a cover on it. Every chapter ends with something you do, and the chapter after it assumes you did it. Read it with a pen, your own analytics open, and your phone within reach.

This is a working manual, not a reference book. Every chapter ends with something written down, and the next chapter uses it. Read it in order the first time, keep a folder for the outputs, and put a date on everything you produce.

This manual is built to be worked with a pen in your hand and a folder open beside you. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single plan with dates. Nothing here needs a developer until chapte

This manual is built to be worked rather than read. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single dated plan.

This is eighteen chapters in five parts, and it is built to be worked rather than read.

This manual is built to be worked with a pen in your hand and your own records open beside you. Keep one folder, on paper or on screen, and put every output in it as you go. Thirteen chapters produce thirteen documents, and the last chapter

This manual is built to be worked with a settings page open beside it. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce a small stack of written decisions, and the last chapter turns th

This manual is built to be worked with a pen in your hand and a booking platform export open beside you. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the las

This manual is built to be run, not read once. Keep one sheet per site and one row per day, and put every value you measure into it as you go. Fourteen chapters produce one checklist, one log, one incident record and one report, and chapter

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single dated plan.

This manual is built to be worked with a pen in your hand and your booking software open beside you. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last ch

This guide turns the Magento admin into a set of simple, repeatable tasks for the non-technical store owner. Written to you in plain American English, it covers logging in safely, reading the dashboard, and the five jobs you do most: proces

Generative AI engines now answer the questions your customers used to type into a search box. This guide shows the exact, layered method AppWT uses to make a business findable, citable, and recommended by tools like ChatGPT, Perplexity, Goo

A plain-English cyber security playbook for small business. Written from real incidents AppWT remediated, with checklists, hardening steps and an incident-response runbook.

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter puts them on one calendar with dates

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Thirteen chapters produce thirteen documents, and the last chapter turns them into a single plan with d

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled sheet, a written policy, a script you have said out loud,

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into one scorecard, one c

Work this manual at a desk, with a calculator and a couple of uninterrupted hours. Eighteen chapters sit in five parts, and each one ends with a document rather than a feeling. A completed sheet, a policy you can hand to a new staff member,

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and together they are the operating file for the business

This manual is built to be worked with a pen in your hand and a phone beside you, because several chapters ask you to call somebody. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fou

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled sheet, a written policy, a script you have said out loud,

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Eighteen chapters produce eighteen documents, and the last chapter turns them into a single plan with d

Read chapter one first. After that this is a work file rather than a story, and you can take the parts in the order your practice needs. Each chapter ends with something you write down, so keep a folder open beside you.

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single ninety-day

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in four parts, and every chapter ends with something you can hold. A filled sheet, a written policy, a script you have said out loud,

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled sheet, a written policy, a script you have said out loud,

This manual is built for a desk, a calculator and about ninety minutes at a time. Seventeen chapters sit in four parts, and each chapter ends with something you can hold: a filled sheet, a written policy, a script you have said out loud, a

Read this one with a pen beside you and a folder open to organize/organise what comes out of it. Almost every chapter ends in a document, a script or a written number, and the book only works if those things get made. Eighteen chapters, fou

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled table, a written policy, a script you have said out loud,

This is a working manual rather than a book you read once. Eighteen chapters, five parts, and one written output from each chapter. If you finish holding a folder of pages with dates on them, the book did its job. If you finish agreeing wit

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled sheet, a written policy, a relabeled shelf, or a template

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single year on one

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Seventeen chapters produce seventeen documents, and the last chapter turns them into a monthly sheet an

This manual is meant to be worked with a pen, not read once on a couch. Each chapter ends with one document, one number or one written rule, and the next chapter asks for it by name. By the last page those pieces sit together as a practice

This manual is built for a desk, a folder of invoices and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled cost card, a written procedure, a script you have

This manual is built for a desk, a calculator and about ninety minutes at a sitting. Eighteen chapters sit in five parts, and every chapter ends with something you can hold. A filled worksheet, a written policy, a script you have said out l

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Thirteen chapters produce thirteen documents, and the last chapter turns them into a single plan with d

This is a working book, not a book for the couch. It is built to be opened at the chapter you need, with a pen beside it. Every chapter ends with something written down, and the next chapter assumes you wrote it. Eighteen chapters sit in fi

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce fourteen documents, and the last chapter turns them into a single plan with d

This manual is built to be worked with your own site open in one window and a plain HTTP request in the other. Fourteen chapters produce one repaired page and one written record, and the last two chapters turn that into a routine you can ke

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Twelve chapters produce one specification, and the last chapter turns it into a checklist with dates on

This manual is built to be worked with a browser open and a spreadsheet beside it. Thirteen chapters produce one folder of outputs, and the last chapter turns that folder into a seven-session plan with dates on it. Keep everything you make.

This manual is built to be worked with a pen and a phone beside you. Keep one folder, on paper or on screen, and put every output in it as you go. Thirteen chapters produce a destination map, a proof, a rollout plan and a monthly sheet, and

This is a working manual rather than a book to read through once. Keep one folder for your show, on paper or on screen, and put every output in it as you go. Thirteen chapters produce a word list, a style sheet, a page template, a triage sc

This manual is built to be worked, not admired. Keep one folder, on paper or on screen, and put every output in it as you go. Thirteen chapters produce a small set of documents, and the last chapter turns them into one dated plan.

This is a short book about a subject people think they already understand. Read Part One in order, even if you only care about running a site, because Parts Two and Three both lean on it. After that you can go straight at the problem in fro

This primer is built to be read once in order and then used as a reference. Twelve chapters, three parts, and a short list of takeaways at the end of each one. If you have ten minutes rather than an evening, read chapter 10 and then set up

This manual is built to be worked with a pen and a spreadsheet open. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce a small stack of documents, and the last chapter turns them into on

This primer is built to be read with a browser open beside it. Fourteen chapters, three parts, and a short list of actions at the end of each one. If you have twenty minutes, chapter 10 tells you the five settings to change once, and you wi

This is a short book meant to be used rather than admired. Thirteen chapters, three parts, and about an afternoon of reading. Keep a pen with it, because six of the chapters ask you to write something down, and the last one asks you to prin

This is a short manual about one habit, so it is built to be read once and then used as a reference. Fourteen chapters, three parts, and a small number of things to actually do. Keep a note or a folder as you read, because five chapters end

This primer is built to be worked through with a phone in one hand. Twelve chapters, three parts, and a short list of actions at the end of each one. If you have an hour, chapter 9 tells you exactly which accounts to spend it on and in what

This manual is built to be worked with a pen in your hand. Keep one folder, on paper or on screen, and put every output in it as you go. Fourteen chapters produce a short stack of documents, and the last part turns them into a plan somebody

This is a short manual built to be worked rather than read once. Fourteen chapters, three parts, and a set of outputs you can keep. By the end you should have a device settings sheet, a written routine, a one-page policy if you employ anyon

This is a short manual and it is built to be worked rather than read once. Keep a single page beside you, on paper or on screen, and write on it as you go. By chapter 12 that page becomes your keep list, which is the one document this book

This is a short book meant to be worked rather than read straight through. Twelve chapters, three parts, and nothing in it takes longer than fifteen minutes to do. Keep one note open beside you, because several chapters ask you to write a s