Current system state
Architecture and public-site position
The current Exos web platform is a custom PHP and MySQL CMS designed around reusable page records, structured section data, and dedicated content tables for major business objects. It supports editable pages, reusable homepage sections, products, services, leadership profiles, clients, case studies, testimonials, media-backed resources, blog posts, newsletter subscribers, contact submissions, navigation menus, and global settings.
Operationally, this means Exos now has a maintainable content system rather than a fixed marketing site. Strategically, the site is capable of presenting Exos as a focused telecom BSS transformation firm with product depth, service clarity, proof content, and editorial authority. The main remaining gap is aligning this stronger CMS-led experience with the primary public-domain strategy.
Stack snapshot
Technical specification summary
- Server-side stack: PHP application with custom templates and helper functions.
- Database: MySQL schema with dedicated tables for pages, sections, services, products, team, clients, case studies, testimonials, insights, newsletter, media references, settings, navigation, and users.
- Editor experience: Admin dashboard with TinyMCE-powered rich text editing on long-form content fields.
- Assets: Uploads stored under
assets/uploads, with document handling for PDF, Office, archive, image, audio, and video formats. - Deployment: GitHub Actions rsync workflow to
/home/exos/public_html/plus direct SSH deployment when needed.
Public capability
What the site now supports
- Homepage with stronger buyer-stage CTAs and above-the-fold trust signals.
- Dedicated listing and detail pages for products, services, people, clients, and flagship items.
- Proof layer through case studies and testimonials.
- Insights Hub with directories, resource pages, blog posts, and newsletter capture.
- Media-driven resource presentation with optional thumbnails and file-type fallbacks.
Operational map
Core CMS data model
| Area | Purpose | Key notes |
|---|---|---|
| Pages and Sections | Controls base page metadata and reusable content blocks. | Useful for homepage hero, reusable messaging, and SEO updates. |
| Products and Services | Drives listing pages, detail pages, flagship surfacing, and homepage promotion. | Supports slugs, rich descriptions, SEO fields, and feature flags. |
| People and Clients | Adds human proof, leadership credibility, and customer visibility. | Includes LinkedIn-based fields for people and dedicated profile pages. |
| Insights, Resources, Blog | Creates a structured authority layer. | Resources and blog posts include publish and approval controls. |
| Newsletter and Submissions | Captures leads and interest. | Newsletter storage is ready; outbound email infrastructure is still placeholder-only. |
Marketing review
What is stronger now
- The messaging is better aligned to telecom BSS modernization, billing transformation, TM Forum integration, and AI-ready operations.
- Calls to action are more decision-stage aware and less generic.
- The site now has the beginnings of proof density through clients, people, case studies, and insights.
- Exos can now publish opinionated content and downloadable material in a way that supports enterprise credibility.
Marketing gaps
What still needs work
- The best-performing enterprise sites in this space use more named proof, more consistent case metrics, and stronger asset branding.
- SEO still needs a fuller keyword architecture across all service and product pages, not just the homepage and primary listings.
- The blog and resources section need a disciplined publishing cadence or they will quickly look dormant.
- Lead capture exists, but attribution, analytics, and automation are not yet complete.
Assessment
Technical and commercial readiness snapshot
| Area | Status | Comment |
|---|---|---|
| Content architecture | Strong | The content model is broad enough for current Exos needs. |
| Admin maintainability | Strong | Routine updates can be made by editors without code changes. |
| Brand and UX quality | Improved | The site now feels more deliberate and credible in-market. |
| Proof maturity | Needs work | Real logos, metrics, and approved outcomes should replace placeholders. |
| Marketing operations | Needs work | Analytics, CRM integration, and publishing rhythm should be formalized. |
| Domain strategy | Important | The strongest build should become the clearly authoritative public experience. |
Future steps
Recommended technical and marketing roadmap
- Make one production environment canonical and migrate all public SEO signals to it.
- Add analytics, CRM integration, and event tracking for CTAs, downloads, blog engagement, and forms.
- Build a branded proof library: client logos, screenshots, downloadable decks, and quantified case-study metrics.
- Expand structured SEO coverage across every product, service, person, client, and insight page.
- Add role clarity and editorial process so approval-based sections stay disciplined rather than ad hoc.