Skip to content

04Web Development

Web Development with Next.js & React

Client-facing applications where the hard part is the data model, not the pixels. Portals, internal tools, and anything replacing a spreadsheet that six people fight over.

Staged releases

04.1 What it covers

  1. Next.js App Router applications, server-rendered by default, typed end to end.

  2. Client portals: document intake, status, deadlines — the things clients currently phone about.

  3. Internal tools that replace a shared spreadsheet, with the permissions the spreadsheet never had.

  4. Postgres schemas designed before the screens, because the data model is the part you cannot refactor cheaply.

  5. Auth, roles and audit trails treated as features rather than afterthoughts.

04.2 How the work runs

  1. Model the data

    Entities, relationships and the rules that are actually invariants. Written down and agreed before any UI exists.

  2. Ship a thin slice

    One complete path through the app, deployed, so the shape is real rather than described.

  3. Build in stages

    Feature by feature, each one released rather than accumulated, so nothing waits on everything.

  4. Hand off

    Architecture notes written up alongside the code.

04.3 Tools

  • Next.js
  • React
  • TypeScript
  • Postgres
  • Auth

04.4 Other services

  • GoHighLevel Development

    The layer under snapshots: custom dashboards mounted inside the platform, marketplace apps with their own OAuth, provisioning that runs on a schedule, and API v2 work that survives a rate limit.

  • n8n & Workflow Automation

    A manual process, written down until it stops having exceptions, then rebuilt as a pipeline with retries, an exception queue and a log someone can read at 8 a.m.

  • Mobile App Development

    One codebase, both stores, built for the case where the network is not there. Sync conflicts get designed, not discovered.