Problem
A products-and-services business usually exists online as a brochure that nobody can update. The catalogue lives in a PDF, consultancy is explained on a social page, and every inquiry arrives with too little context to answer — so the first reply is always a request for information the site could have asked for.
Our role
Design, build, and the content model behind the public pages.
Approach
TanStack Start provides the routing and server rendering, with React and TypeScript on top and Supabase behind for content and inquiries. Products and consultancy services are records rather than pages, so a catalogue change is an edit in the administrative side and not a release.
Inquiries are captured as structured submissions — the fields the business actually needs — so an answer can be prepared from the message itself. The administrative side records who changed what, which matters more for a catalogue than for most content, because prices and availability change often.
Off-site backup using Cloudflare and object storage is designed but not claimed as running; it is listed as architecture, not as a feature.
Outcome
The public content, product and service presentation, and the inquiry path are built. Order and customer-facing workflows exist only in part, and the backup plan is a plan. Splitting those three levels apart is the honest description.
Notes
Approved brand imagery is a prerequisite before this page carries screenshots. No customer inquiries or order records are reproduced here.