Sustainability Assessment Platform - Custom Next.js + Supabase Build.
Custom web application development for a sustainability assessment workflow that needed structured data, collaboration, auto-save, and report generation.
Modern web app build
Reduced data loss risk
Teams and roles
Assessment-ready documents

The challenge
The client needed to turn a complex assessment process into a usable web application. The existing workflow relied on documents, spreadsheets, and manual consolidation. That worked at small scale, but it created version-control problems, repeated admin, and too much risk of incomplete or inconsistent submissions.
The product needed to support multiple organisations, team members, structured questions, evidence uploads, progress saving, and report generation. It also needed to be simple enough for non-technical users to complete without training.
Success meant shipping an MVP that could be used with real customers, not a throwaway prototype. The build needed clean authentication, a durable data model, auto-save, role-based access, and a path to future product features without needing a full rebuild.
The approach
Discovery and validation
The first phase mapped the assessment workflow and separated must-have product behaviour from nice-to-have reporting ideas. That kept the MVP focused: capture clean data, let teams collaborate, prevent lost work, and generate a usable output.
Architecture
Next.js and Supabase were chosen because the project needed a fast web app, Postgres-backed structure, authentication, storage, and room to iterate without building a heavy custom backend from scratch. The schema was designed around workspaces, users, assessments, responses, evidence, and generated reports.
Build phases
The first build shipped authentication, workspace setup, assessment navigation, and response capture. The second phase added auto-save, progress states, evidence uploads, and review logic. The final phase focused on PDF output, QA, and admin workflows.
Operational polish
The details mattered: clear empty states, autosave feedback, validation, sensible permissions, and the ability for internal users to inspect progress without disturbing client work. Those are the parts that decide whether an internal product gets used or quietly abandoned.
The results
The MVP replaced a manual assessment workflow with a structured application that could support real users, team access, and repeatable report generation. The value came from reducing operational drag rather than adding unnecessary product complexity.
Because the app was built in phases, the client could validate the core workflow before committing to a larger roadmap. The architecture left room for richer reporting, billing, and customer-facing dashboards later, but the first release stayed focused on the work that needed to happen now.
What did not go perfectly
The first release deliberately avoided overbuilding analytics and billing. Those features make sense once enough real usage data shows what customers need from the product after assessment completion.
Project gallery
Screenshots and project visuals from the build, optimisation, or platform work.



Related case studies
More examples across ecommerce, platform work, and custom development.

Premium Skincare Paid Media Strategy
Full-service Shopify growth strategy for a premium skincare brand where store optimisation, email, and paid media needed to work from the same numbers.
Read case study →
Luxury Furniture Shopify B2B Build
Custom Shopify B2B build for a premium Yorkshire furniture brand selling high-value products to retail and trade customers.
Read case study →
Yorkshire Fashion Retailer Shopify Migration
Shopify migration and conversion optimisation for an established Yorkshire fashion retailer outgrowing a slow, hard-to-measure ecommerce setup.
Read case study →Got a project like this?
Book a free 30-minute Discovery call. We will talk through what is possible for your business and whether I am the right person to deliver it.
