Hustle #003 / Work for Good

Work for Good: eight steps, one build.

A free UK work-experience idea became a private demo. The founder decisions, account handoffs and security checks are part of the build.

What we did

01 / Choose one customer

27 September / 5:06pm onwards

A placement route for young people.

  • The founder described the work-experience idea. Students would find UK placements lasting one day, several days or a week.
  • The founder chose a web-first product. The first version would be a website rather than an app.
  • The founder named the project The World of Work. The name carried into the private concept demo.
02 / Check the idea and the costs

27 September / the first discussion

Free access, with checks built in.

  • The founder rejected charging either side. She wanted the service free for students and businesses.
  • The founder required parent approval. A young person's signup needed a parent in the loop.
  • The founder required business review. Businesses needed owner review before posting opportunities.
  • The founder required safeguarding checks. These were a launch condition, not something the demo could prove.
03 / Give it a name and a home

27-28 September

Create the project and its private home.

  • The agent attempted Supabase signup. An image-based robot check stopped the account flow on 27 September.
  • The founder completed Supabase signup. She confirmed "Supabase done" at 11:25pm on 27 September.
  • The founder created the Supabase project. She supplied its project URL at 11:30pm that evening.
  • The agent checked the authentication service. The Supabase service responded, but that did not mean the application logins were connected.
  • The agent deployed the gated website. The 28 September update reported theworldofwork.uk online behind a sign-in gate.
04 / Make one thing people can buy

27 September / private concept

Show the journeys before connecting real users.

  • The agent built the student concept screens. The demo showed the placement-search and matching idea.
  • The agent built the business concept screens. The demo showed how an opportunity could be listed.
  • The agent built the admin concept screens. The demo showed the review role.
  • The founder requested separate login buttons. She asked for student and business entry points at the top.
  • The agent marked the login buttons demo-only. The concept buttons were not presented as working account access.
05 / Put it in front of real people

28-30 September / demo preparation

Prepare the controlled demo.

  • The agent prepared the database schema. The handoff covered seven tables with restricted access.
  • The agent wrote the verification script. It supplied a separate SQL check for the founder to run after the schema.
  • The agent prepared the seven-table database checks. The handoff separated schema setup from the later checks needed before real accounts could use the app.
  • The agent prepared the Wednesday demo. The 2 October report recorded that the demo had been built and shown on Wednesday.
06 / Learn from the first response

1-2 October / after the demo

Close the demo before real-login testing.

  • The founder asked to lock the website again. On 1 October, she said "Lock it and start on real log in testing".
  • The agent checked the gate after the demo. The dated follow-up recorded the hosts redirecting to the gate.
  • The agent scoped role-based login tests. Student, parent, business and admin accounts needed separate data-access checks.
07 / Hand over one repeatable job

1 October / the testing handoff

One owner check before the next tests.

  • The agent attempted the Supabase dashboard check. A human-check stopped sign-in, so the backend check did not complete.
  • The agent wrote a read-only SQL handoff. The founder could run it in Supabase SQL Editor and return the results.
  • The agent separated testing from public signup. The login form would stay off until the role and database checks were proved.
08 / Improve it, change it or stop

2 October / still private

Keep the remaining work visible.

  • The agent reported the testing blocker. The 2 October update said the Supabase SQL results were still needed before fictional-login and security tests.
  • The agent scoped the kids-data checklist. The checklist was planned before any real signups.
  • The agent scoped the EU AI Act review. The compliance review was planned after backend testing, not described as already passed.
5 November 2026

Today's update

  • The build went live on its own domain on 8 October behind a pre-launch boundary: new signup off, hidden from search, and a production database change applied and read back. The pilot is scoped without employer AI ranking.
  • It is built and tested with fictional users and placements only. A mobile layout failure found in review was repaired and checked at phone size.
  • Thirteen notification emails were written, independently reviewed and approved. In a controlled test they were sent only to the founder's own inbox: eleven arrived and two were rejected by the mailbox provider's authentication check. After a missing DNS authentication record was added, the two were retried and delivered. No other external email has been sent.
  • A review found a real gap before launch: a student withdrawing an accepted application did not notify the business. It is fixed.
  • Real child intake stays closed, scheduled sending is off, and queued test emails are held or cancelled.
The biggest snag

Biggest learning

  • "Email works" has to be proved per provider and per message.
  • A reviewer reading the flow end to end catches gaps that tests on fake data miss.
The next test

Next step

  • Finish the remaining launch checks before any real intake. No customer or traction claims.