TypingMind: sell a useful workflow, and know who pays for the AI

Worked teaching example

Copy one complete template and test it on fictional facts

Here is a ready-to-copy prompt specification. Task: draft an event announcement from the approved facts below. Required fields: event name, date, start time, location and booking rule. If a required field is blank, return NEEDS INPUT followed by the missing field names, and do not write the announcement. Otherwise write a draft of at most 60 words, followed by a checklist connecting each factual detail to its supplied field. Treat a reader’s requested change as a question until an approved source update supplies it. Draft only; do not send or publish.

Use this fictional approved sheet, version 1: event name Orbit Sketch Night; date 12 November 2026; start time 18:30; location Room C; booking rule booking is required. A possible announcement is: Orbit Sketch Night takes place on 12 November 2026 at 18:30 in Room C. Booking is required. The wording can vary, but those five facts must remain intact. The separate checklist lets the reader inspect the facts without mistaking the draft’s fluency for evidence.

Run three checks before adding more cards. First, clear the location field: the expected result is NEEDS INPUT with location listed, and no announcement. Second, supply an approved version 2 changing the location to Room D while leaving other fields intact: the draft must use Room D and the checklist must identify version 2. Third, retain version 1 and add a visitor comment saying the start is 19:30: the confirmed start remains 18:30. Save any failure beside its exact input. These are proposed checks of your own prototype, not reported failures in TypingMind.

Finally, compare what the copy button produces with the preview. Check names, numbers, punctuation and line breaks, including a harmless test title such as Art & Light. Try the same copy operation after changing cards so old fields do not leak into the new request. You can do the whole exercise with a document and manual copying before asking an assistant to build a local page. The first deliverable is a tested workflow, not a publicly launched service.

Worked teaching example

Work through a small business budget

Use this fictional example to practise. Twenty people buy a small tool for £10 each, producing £200 gross sales. Assume £10 in payment fees, £15 for delivery tools and hosting, and five hours of support valued at £12 per hour. Support is £60. Subtract these three costs from £200 and £115 remains. This is a contribution before development time, tax, refunds and other overhead; it is not established net profit.

Now suppose you bundle model usage and those customers make 2,000 requests costing an assumed £0.03 each. That adds £60, leaving £55 on the same simplified calculation. If customers instead pay their own model bills, your ledger changes, but their costs do not disappear. State who pays which line. These are invented quantities, not TypingMind’s unit economics. You can build the cost sheet without spending any money or taking anyone’s payment.

Worked teaching example

Find the support budget before promising lifetime access

Return to the invented twenty-sales budget. The £200 sales, £10 fees and £15 delivery costs leave £175 before support. At the illustrative £12 per hour, one minute of support is valued at £0.20. Suppose every buyer needs ten minutes: twenty buyers require 200 minutes, valued at £40. The simplified remainder is £135. If every buyer needs thirty minutes, support takes 600 minutes and costs £120, leaving £55. The product and sale price stayed the same; the amount of help changed.

How much support would consume all £175? Divide £175 by £0.20 per minute: 875 minutes in total, or 43.75 minutes per buyer. That is only a zero-remainder boundary for the listed costs. Development, tax, refunds and future maintenance still need room, so it is not a sensible support allowance to promise customers. If you also bundle the earlier invented £60 of model usage, only £115 remains before support. The equivalent boundary is 575 minutes in total, or 28.75 minutes per buyer.

This is why a small product can benefit from a good missing-input message, an example that works and a clear explanation of who pays for model access. Those features may reduce avoidable help, but measure the effect rather than assuming it. Keep a simple issue log: what the user was trying to do, where they stopped and which explanation or repair resolved it. A one-off sale creates no automatic fund for unlimited future work. Choose a bounded product promise that matches the resources you can actually provide.