01 / 03 Concept studyClose 
2026Apps, Portals & DashboardsConcept study
Orbit OS
Operations-heavy services business
The business had tools for everything and a view of nothing.
- React
- Supabase
- OpenAI
- Recharts
- Client
- Operations-heavy services business
- Timeline
- Ten weeks
- Discipline
- Apps, Portals & Dashboards
- Scope
- Product strategy, Interface systems, Interaction design, AI workflow architecture
01The brief
Operations data was spread across a CRM, a project tool, spreadsheets and a dozen automations. Leaders asked for a weekly report that took a full day to assemble.
Operations overview01 / 0302What we built
An operations platform with a live overview, a workflow library and assistants for sales, revenue and knowledge work. A cobalt identity gives a complex system a recognisable centre.
Pocket overview02 / 0303How it connects
Every existing tool reports into one data layer. Assistants act on the same records the team sees, so nothing happens in a black box.
04What changes
- The weekly report writes itself.
- Everyone works from the same numbers.
- Assistant activity is visible and reversible.
Interface system03 / 0302 / 03 Concept studyClose 
2026Apps, Portals & DashboardsConcept study
Keystone
Architecture and build firm
Clients asked the same question every week: where are we, and what do you need from me?
- Next.js
- Supabase
- Stripe
- Resend
- Client
- Architecture and build firm
- Timeline
- Nine weeks
- Discipline
- Apps, Portals & Dashboards
- Scope
- Service design, Portal UX, Payments, Notification system
01The brief
Drawings went out by email, approvals came back by phone and invoices lived in accounting. Projects slipped while decisions waited in someone’s inbox.
Project portal01 / 0302What we built
A portal for each project with a live timeline, approval requests with deadlines, a drawing register, site photo updates and invoices that can be paid in place.
Approval on mobile02 / 0303How it connects
The portal reads from the firm’s project tracker and accounting, so the team updates one system and the client sees it straight away.
04What changes
- Approvals come back faster because they have a deadline and a button.
- Clients stop asking where things stand.
- Invoices are paid from the same place as everything else.
Interface system03 / 0303 / 03 Concept studyClose 
2026Apps, Portals & DashboardsConcept study
Tideline
Charter and boat tour operator
Every windy morning meant two hours of phone calls to move trips around.
- Next.js
- Supabase
- Stripe
- Twilio
- Client
- Charter and boat tour operator
- Timeline
- Twelve weeks
- Discipline
- Apps, Portals & Dashboards
- Scope
- Operations mapping, Booking engine, Fleet scheduling, Guest app
01The brief
Bookings came from three websites, crew rotas lived on a whiteboard and weather changes were handled by calling every guest one by one.
Fleet board01 / 0302What we built
A fleet board that shows every boat, trip and crew member by day, a booking engine that respects capacity and a guest app with check-in, directions and live updates.
Guest app02 / 0303How it connects
The weather feed flags trips at risk. Rescheduling a trip updates crew, guests and payments together, and guests choose a new slot from a link.
04What changes
- Rescheduling a morning takes minutes, not phone calls.
- Double bookings stop because capacity lives in one place.
- Guests know where to be and when.
Interface system03 / 03