IntelliSend
Marketing site and core application for an SMS delivery platform
Frontend engineering across both sides of a SaaS product that routes and switches SMS providers in real time — the public marketing experience, and the dashboards, tables and workflows inside the application.
- Frontend Engineer · Contract
- 2025
- Shipped
Overview
A part-time contract covering both the marketing surface and the product itself. On the marketing side: the landing page, responsive sections, and the product presentation that has to make real-time provider routing legible to a non-technical buyer. On the product side: dashboard interfaces, data widgets, tables and user-facing workflows — data-heavy screens where the work is keeping dense information scannable and easy to act on. Also contributed the reusable component patterns the application builds on.
Problem
Real-time SMS provider routing is a hard thing to sell and a hard thing to operate. The marketing site has to make an invisible infrastructure feature legible to a buyer, and the application has to make routing state and delivery data readable at a glance to an operator.
Approach
Treat both surfaces as one system. The same component patterns and layout language carry from the landing page into the dashboard, so the product does not feel like a different piece of software than the site that sold it.
Key interactions
- Landing page built responsive-first, with the product presentation carrying the technical story
- Dashboard interfaces and data widgets for delivery and routing state
- Data tables built to stay scannable as row counts grow
- User-facing workflows translated from design to production frontend
- Reusable component patterns shared across marketing and product
What I took from it
- Data-heavy UI is mostly an editing problem — deciding what not to show is the work.
- Carrying one component language across marketing and product saves more time than any individual abstraction.