Write a one-page brief
Before talking to any developer, write: who it is for, the three things they must be able to do, what exists already, and your rough timescale. One page is enough and saves weeks.
Resources
Free notes from the workbench.
Tell us where you are in your project and we will show only the notes that help right now. Useful whether or not you ever hire us.
I am…
8 guides shown
Decide what can wait
List every feature idea, then mark each “launch”, “soon” or “someday”. Most first versions only need the first column. Accounts, chat and payments are often the costliest “someday” items.
Test your wording, not just your layout
Ask three people to complete a task while thinking aloud. Note every word they hesitate over. Rename buttons after the action they perform: “Send invoice”, not “Submit”.
Five accessibility checks anyone can do
Zoom the page to 200%. Tab through with the keyboard only. Turn on your phone’s largest text size. Check text contrast with a free checker. Make sure every image that matters has alternative text.
App store readiness checklist
Prepare: app name and subtitle, a description that matches what the app really does, screenshots for required device sizes, a privacy policy URL, accurate data-collection declarations, a support contact and test login details for reviewers.
Keep your accounts in your name
Register Apple Developer and Google Play Console accounts, domains and hosting under your organisation. Give contractors access through team roles rather than sharing passwords.
When a website form goes quiet
Check the mailbox exists and is not full, look in spam, confirm the domain’s mail records with your host, and send a test from a different address. “Sent” on a website usually means accepted by the server, not delivered.
Basic security hygiene for small teams
Use a password manager, turn on two-step verification for email and domain accounts first, keep devices updated, and remove access promptly when someone leaves.