NOBS is a production system built to run NOBS

It's easy for a studio to talk about building "real systems" while its own website is a handful of static pages and a contact form. NOBS doesn't have that gap. The site is a full Next.js application backed by a real Postgres database, and the business itself runs on it day to day, not just the marketing pages in front of it.

Underneath the pages a visitor sees, there's an authenticated client portal separate from the public site: clients log in to see their own project's progress, milestones, uploaded files, and a message thread with direct back-and-forth, no shared inbox, no lost email threads. Authentication is role-based, so a client account and an admin account see entirely different surfaces of the same application.

The admin side is a working operations dashboard, not a CMS demo: portfolio and blog content, client records, bookings, incoming inquiries, and payments all get managed from inside the same system that's serving the public site. Payments for bookings and invoices run through the same Paystack and Flutterwave integrations built into client projects, because there's no reason the business behind NOBS should trust a worse payment flow than its clients get.

None of this is exposed publicly in a way that risks client data, and it isn't meant to be a tour of the codebase. It's mentioned here because it's the most honest kind of proof available: the discipline that goes into a client's admin dashboard, database design, and ongoing operation is the same discipline running this business, because it's the same application.