Skip to content

Project 18 / 25

Marketing software / Web app

CondoRoyalty Email

Interface with sample data

An $800+ monthly email bill and poor inbox placement prompted a custom platform: familiar templates, HubSpot contact sync and carefully controlled sending through Amazon SES.

The problem & the solutionTry live demo

Composing an email and previewing it on mobileSample data

My role
Product design & development
Built with
  • Next.js, Framework
  • React, Frontend
  • TypeScript, Language
  • PostgreSQL, Database
  • Amazon SES, Email delivery
  • HubSpot, CRM
In focus
  • Visual email builder
  • Audience management
  • Campaign reporting

An expensive email bill. A delivery problem.

The challenge

As the contact list grew, HubSpot email marketing cost $800 or more a month. The owner also reported campaigns landing in spam. Paying more was not solving the delivery problem, and a generic email tool was not a good fit for the team's day-to-day property marketing.

Before
$800+ / month

A growing email bill, with campaigns reportedly reaching spam.

After
A platform of their own

Purpose-built campaigns and direct sending through Amazon SES.

The previous bill is owner-reported. Current costs and delivery rates were not independently audited.

A builder for property marketing, not every possible use case.

The team's familiar layouts became a reusable template library. Custom blocks and widgets make property launches and announcements easier to assemble. Campaigns can be scheduled or sent immediately, without rebuilding each message from scratch.

Template library

Behind a simple Send button, a careful delivery system.

The existing contact database was imported and new HubSpot form contacts continue to sync automatically. Sending began from a new subdomain, with gradual batches and previously engaged contacts first. The platform reacts to Amazon's feedback, blocks failed addresses, stops campaigns when the configured bounce limit is reached, and honors unsubscribes immediately without an extra confirmation step.

How the system works
  1. HubSpot contacts
  2. Engaged contacts first
  3. Gradual batches
  4. Amazon SES
  • Pause at the bounce limit
  • Suppress failed addresses
  • Apply unsubscribes immediately

A workflow the team can actually use every day.

Campaign creation, contact management and engagement reporting live together. The result is more than a replacement email editor: it is a sending workflow tailored to this business. These practices help manage sender reputation; they do not guarantee an inbox placement for every message.

Campaign engagement

The difference

The team gained a simpler campaign workflow and an alternative to the growing email subscription bill. The owner reports better delivery and a better fit for daily work, with templates, contacts and sending safeguards in one place.

Business context and reported outcomes were supplied by the project owner. Screens and the public demo use sample data; no client audience or live sending credentials are exposed.

Something worth building?

Tell me what you have in mind.

Let's talk