A method · 25 October 2026

What to hand over before anything is built.

Most disappointing apps from a chat fail before a single file exists. The sentence was too thin. “Make a CRM” can mean twelve products. The model will pick one, cheerfully, and it will be the one you didn’t mean.

You do not need a specification. You need four lines. Paste them at the top of the chat and tell it to turn them into a blueprint, not into code.

1. Who it is for

One person, in one situation. “A hike leader checking the ridge at 7am”, not “outdoor enthusiasts”. The second phrase invites a brand campaign. The first invites a screen.

2. The one job

What they do in under a minute. “See if the wind is silly, and decide to go or stay.” If you have three jobs, you have three products. Ship the first.

3. The screens

Name them like a storyboard, not like a database. Today. This afternoon. Don’t go. A caption each: what is large, what is quiet, what is missing when there is no signal. If you have a sketch or a photo, attach it. Pictures beat adjectives.

4. What it must not do

This line saves you. No account. No social feed. No map that needs a key you do not have. No dark pattern that asks for a card. Constraints are how a non-coder art-directs.

Then say: make the blueprint. Do not write the app in the chat. Send it to BitBytec.

The blueprint is a zip or a short description: title, summary, those screens, those pictures. Your Mac shows it back to you. If the chat invented a fifth screen called “community”, you will see it, and you can say no before anyone builds it.