HumanLed

Process

1. 1.Identified the problem

   I saw a need for creators to show that work could still reflect real human authorship, judgment, and creative process even when AI or other tools assisted.

2. 2.Defined the product

   I shaped HumanLed around a simple shareable link rather than an AI disclosure form, score, or percentage system.

3. 3.Designed the experience

   I determined what creators should be asked, how their contribution and tools should be presented, and how the public link should function as a portfolio and evidence layer.

4. 4.Built and tested the MVP

   I worked through the product flow, tested links with different types of work, identified where the experience felt confusing or too technical, and directed revisions.

5. 5.Refined the product

   I simplified the language, added portfolio-style public pages, contextual tool suggestions, automated work previews, and clearer dashboard link management.

6. 6.Shipped the product

   I guided implementation, reviewed migrations and release plans, tested production behavior, and approved each phase for deployment.

Tools used

• Cursor
• Supabase
• Next.js
• Render
• Cloudflare
• Resend
• React
• GitHub

How the tools helped

Cursor assisted with implementation, technical planning, debugging, code review, migration design, and testing. Supabase provided authentication, database, security policies, and storage-ready infrastructure. Render hosted the application, Cloudflare handled the domain and email routing, and Resend supported authentication emails. I directed the product, evaluated the work, chose what to keep or change, and approved each release.

More about the work

HumanLed was developed through repeated use on real creative projects. Each phase was shaped by seeing where creators might feel boxed in, over-explained, or asked to defend their use of tools. The product evolved toward a simpler idea: a HumanLed link shows the work, what the creator contributed, how they worked, and where tools helped.