The situation before the platform
Why an enterprise needed one communication ecosystem instead of scattered tools and informal channels.
| The business |
Organisations running internal communication at scale across departments — the communication owners who write and send updates, and the employees who are meant to read and act on them. |
| The starting point |
Teams relied on scattered tools and informal channels to share information. Updates were missed, messaging was inconsistent, and keeping departments aligned was difficult — with no centralised place to create, send and track internal email. |
| The trigger |
Creating internal emails was time-consuming and needed technical skill, which slowed workflows and limited what non-technical users could produce. At the same time nobody could see how any of that communication actually performed. |
| What they wanted |
One internal email platform combining customisable email workflows, template and campaign management, structured team and audience routing, collaboration tools and a communication analytics dashboard — without depending on external services. |
| Constraints |
The builder had to stay usable for people with no technical background · communication structures had to scale with the organisation rather than be re-modelled per department · reporting accuracy mattered, because engagement data was the basis for changing how teams communicate. |
What it runs at today
The platform as delivered, live and scaling inside organisations.
Four gaps that shaped the build from day one
Not vague pain points — the specific tensions in replacing fragmented internal communication with one structured platform, each paired with what we did about it.
Without a centralised communication system, teams relied on scattered tools and informal channels to share information. That led to missed updates, inconsistent messaging and difficulty maintaining alignment across departments, which affected productivity and collaboration overall.
A single platform where teams manage all their communication needs — sharing updates, coordinating tasks and collaborating in one place, so information flows consistently across departments instead of through separate tools.
Designing and sending internal emails took significant manual effort and technical know-how. Non-technical users struggled to produce structured, presentable emails, which slowed communication and reduced the quality and consistency of internal messaging.
A no-code drag-and-drop email builder with customisable layouts, reusable components and pre-built content blocks, so anyone can assemble a branded internal email quickly without technical expertise.
Organisations had no meaningful insight into how internal communication performed. Without data on open rates, engagement or user interactions, it was hard to evaluate effectiveness, spot gaps or make informed improvements.
Analytics dashboards covering open rates, click-through rates and engagement levels, with downloadable reports so teams can measure effectiveness and act on it rather than guess.
Teams had no structured workflows or guidance to improve their communication practices. The absence of resources and best practice made it harder for employees to build effective communication habits, leaving inconsistency and inefficiency in place over time.
Structured campaign workflows, a template management system and Primary and Secondary Team architecture, so consistent practice is built into the product rather than left to individual habit.
How it fits together
Simplified — the shape rather than every service.
A React.js front end carries the drag-and-drop email customisation, campaign configuration, template management and analytics dashboards in one responsive web application.
A Node.js backend handles every client request along with user roles and permissions and the Primary and Secondary Team structures that decide who receives what.
Each function is its own concern, so campaign automation, templates, reporting and collaboration can be tuned or extended without destabilising the others.
MySQL holds user, team and campaign data, AWS S3 stores shared files and email assets, and AWS SQS queues the processing behind campaign sends so volume does not block the interface.
Six systems doing the actual work
Not a features list — the specific things we built behind every number above.
All internal communication processes sit in a single platform, so announcements, updates and campaigns are managed in one place instead of across disconnected tools.
A no-code builder with customisable layouts, reusable components and pre-built blocks, so non-technical users produce professional internal emails without markup work.
Primary and Secondary Team structures group users and contacts, so messages can be segmented and delivered to the departments or audiences they are meant for.
Interactive dashboards report open rates, click-through rates and engagement levels, so teams can see what works and adjust how they communicate.
File sharing, project coordination, communication tracking and campaign scheduling keep work aligned across the organisation rather than in individual inboxes.
A template management system for branded, reusable communications, paired with campaign configuration so the same standards apply every time a message goes out.
What the platform does day to day
Five capabilities, each closing one of the gaps identified above.
| Capability | Runs | Refresh | What it does |
|---|---|---|---|
| Centralised communication hub | Organisation-wide | Continuous | Brings all internal communication, campaigns and updates into a single platform |
| Drag-and-drop email builder | User-configured | On demand | Enables users to create professional, visually engaging emails without technical skills |
| Real-time communication analytics | Dashboard | Real time | Provides interactive dashboards with insights into email performance and engagement |
| Structured team & audience management | Admin-managed | On change | Enables targeted communication through Primary and Secondary Team structures |
| Collaborative workflow & engagement | Team | Continuous | Combines file sharing, project coordination and communication tracking |
How the moving parts plug in
Delivery, storage, queueing and billing reach the platform through one API layer rather than sitting beside it as separate tools.
Connected capabilities
Platform integration layer
Core services
Because templates, team structures and reporting resolve against the same services, building a communication, sending it to the right departments and measuring how it landed are three steps in one dashboard rather than three separate systems.
What protects employee and organisational data
Internal communication carries employee data, contact lists and payment records for the subscription itself — so access control and reliability were designed in.
User roles and permissions are part of the backend rather than an interface convention, so each person reaches only the campaigns, teams and reports their role covers.
Primary and Secondary Team architecture governs who is in scope for a message, which keeps internal communication inside the intended audience instead of broadcast by default.
AWS S3 holds shared files and email assets while AWS SQS queues campaign processing, so large sends are absorbed by the infrastructure rather than dropped.
Stripe handles payment for the platform itself, keeping billing on a dedicated secure path rather than inside the communication application.
How we got there
Five stages, starting with how organisations actually handle internal communication rather than a feature list.
In-depth research into how organisations handle internal communication — stakeholder needs, existing email workflows and the collaboration challenges behind them.
Communication processes, user roles and campaign workflows were mapped out, and email automation, customisable templates, analytics and collaboration tools prioritised.
Wireframes, prototypes for the drag-and-drop email builder and dashboard layouts, with the emphasis on usability, accessibility and simplifying complex communication tasks.
A scalable architecture bringing together team management, campaign automation, customisable templates, analytics dashboards and collaboration tools as one experience.
Extensive usability testing and feedback cycles: workflows refined, performance optimised and reporting accuracy verified before deployment.
What changed for the business
Beyond the headline numbers, three things teams noticed first.
Fragmented workflows were replaced by a centralised, collaborative platform, so information sharing across departments runs through a single structure.
Teams create professional internal email campaigns without technical help and manage communication structures with far less manual effort.
Detailed analytics dashboards made engagement visible, which is what let organisations hold consistent communication standards across every team.
What the engineering choices are worth in operating terms
Every headline number traces back to a specific decision, not a vague platform effect.
| Engineering decision | Operating outcome | Measured effect |
|---|---|---|
| Centralised communication hub | Updates and campaigns run through one structured workflow instead of scattered channels | 60% better efficiency |
| Drag-and-drop builder & template system | Non-technical users assemble branded internal emails from reusable blocks | 45% faster creation |
| Team structures & analytics dashboards | Messages reach the right audience and their performance is visible afterwards | 35% more engagement |
| Usability testing & workflow refinement | Workflows match how people actually communicate, so the platform gets used | 98% positive adoption |
What it's built on
The actual technologies, not feature names with icons attached.
Frontend
- React.js
- HTML
- CSS
- JavaScript
Backend
- Node.js
- MySQL
Data & infra
- AWS
- AWS S3
- AWS SQS
Integrations
- SendGrid Emails
- Stripe
Get the complete write-up as a PDF
The same content on this page, plus the extended module breakdown and delivery phases, in a single document you can share internally.
- Full platform and communication service architecture
- Discovery-to-deployment process, phase by phase
- Email builder, team structure and analytics decisions in detail
Download the case study
No spam • unsubscribe anytime • we’re here when you need us
Other platform builds