For larger organizations
Sites, portals, and the software behind them
Written for manufacturers, distributors, contractors and coatings companies that run more than one property, or need more than a marketing site. We build the signed-in half as well — and we run one of our own in production.
What we run
We run a multi-tenant client portal in production
Multi-tenant means one application serving many separate client accounts, rather than a copy of the software per client. Ours is live: projects and their status, approvals, documents, invoices, and a social scheduler that stages and queues posts. It is built on Next.js and Supabase — the same stack the websites are built on — which is why the signed-in half of a project is something we build rather than something we send out.
- Named accounts with roles, so what a person sees follows their job — access attached to the person rather than to a link that works for whoever holds it
- Projects, approvals, documents and invoices in one signed-in place, searchable long after the conversation that produced them
- A social scheduler that stages and queues posts for review — nothing publishes on its own
- Built on Next.js and Supabase, the same stack we build client software on, so one codebase serves the public site and the private one
What a build at this size usually includes
Marketing sites
The public site: fast, findable, and specific enough that a buyer can tell what you make.
Dealer and distributor portals
A signed-in area where each account reaches its own price list, documents, and order history.
E-commerce with account pricing
A storefront that knows which account is signed in and prices accordingly.
Internal tools
The screens your staff work from — status, uploads, approvals, and a record of what changed.
Multi-brand systems
One design system across every brand, division, or product line you own.
Connections to what you already run
Where your ERP, CRM, or job system has an API — a way for two programs to exchange data directly — what we build can read from it so nobody rekeys anything. Where there is no API, we show you the options first.
Careers and recruiting
Role pages and applications that land with the person who does the hiring, in a format they can act on.
Ongoing care
Updates, fixes, content, and improvements after launch, picked up in the order you rank them.
One design system across every property you own
A design system is the shared set of components, type, and color that every page gets built from. When a company runs several sites — divisions, subsidiaries, product lines, a careers site — the system is what keeps them recognizably one company without turning them into the same page.
- One set of components and tokens, so a brand change lands everywhere it appears
- Each property keeps its own content, its own domain, and its own analytics
- New pages get assembled from parts that already exist and have already been tested
- The code stays conventional and readable, so it can be picked up by another developer without a rewrite
Standards
Accessibility, speed, and security are part of the build
- Keyboard paths, focus order, color contrast, and screen-reader labels — a screen reader being the software that reads a page aloud — are checked as the pages are made, not bolted on at the end
- Speed is treated as a budget while a page is being built, and checked on real devices rather than assumed
- A modern, maintained stack: Next.js, React, HTTPS everywhere, and dependencies kept current
- Named logins and role-based access anywhere a site has a signed-in area, with single sign-on available where your staff already have accounts
- Semantic markup and structured data, so search engines and assistive software read the same page the same way
How this fits the way you buy
Scope first, then the number
We map what has to exist and who has to sign it off. You get a firm number and a real schedule after the first conversation.
Work under NDA
Some of our work is under NDA. We describe the scope, the market, and the technical challenge without naming the owner — and we hold your work to the same rule.
Shipped in stages
The first release is small enough to check. Every stage after it is agreed before it starts, so nothing large gets built on an assumption.
Two shapes this usually takes
Neither is a package, and neither has a price on it. Both start with the same conversation.
Fixed scope
A project
A defined build — a site, a storefront, a portal — designed, built, and launched against an agreed scope. You get a firm number and a real schedule after the first conversation.
Ongoing
A partnership
Design and development that continues after launch, across the properties you run, with the queue ordered by you. Scoped the same way, renewed rather than re-quoted every time something changes.
Questions we get from larger organizations
Tell us the goal. We'll map the route.
Websites · Client portals · Internal tools · Ongoing care