An internal enquiry and operations platform
An internal agency system that connects a static marketing site to an API for enquiries and operational follow-up.
Business area
Agency operations
Project record
Internal platform
Related services
The situation
What needed attention
A static website should not need to contain private customer records or provider credentials just to handle enquiries.
The response
How the work was shaped
The documented architecture separates Astro marketing pages from a Go API, with SQLite storage and an outbox for downstream work.
Evidence before adjectives
What is documented
Specific features and decisions found in the project record.
Static marketing and management interfaces
Go API for enquiries and operational records
SQLite storage and migration model
Outbox for email and other downstream integrations
Why it matters
The business purpose
The separation offers a useful architectural model when a small business needs a public website and a private workflow behind it.
The repository specifies an application boundary between public pages and private enquiry operations.
Related examples
Explore another project
Kashmir World School
A school website and operations platform
A school website with guardian journeys alongside an administration system for students, fees, exams and results.
In the project
Student admissions, updates and promotion workflows
- Next.js
- TypeScript
- MySQL
XpressSys
Logistics CRM and customer-facing website
Logistics business web presence with a separate CRM engagement for managing operational information.
In the project
Public logistics service website
- PHP (public site)
- CRM application
Working through something similar?
Share the goal, your current setup and what needs to change. We can discuss which part to tackle first.