Skip to main content
EH DESIGNSoftware & Business Solutions

Work

BookedFlow

Lead intake, follow-ups and appointment management SaaS for service businesses. MVP / active development.

Lead and Appointment SaaSWebMVP

Overview

  • Focused on the intake-to-appointment path that service businesses lose in inboxes and spreadsheets.
  • Laravel API and Next.js UI share one MySQL system of record with Redis for queues and cache.
  • MVP scope protects lead capture, follow-ups and appointments — not dispatch, invoicing or GPS.
  • Active development means core flows are being shaped; not marketed as a finished self-serve SaaS.

Business context

Service businesses often capture leads from calls, forms and walk-ins, then lose follow-through because ownership, next actions and appointments live in different places.

Problem

Teams could not see which leads were unowned, which follow-ups were overdue or which appointments conflicted without reconstructing the day from chats and spreadsheets.

Intended users

  • Front-office staff capturing inbound leads
  • Sales or booking coordinators running follow-ups
  • Service managers reviewing appointment load
  • Owners monitoring pipeline hygiene

Core capabilities

Lead intake

Structured capture of contact details, source and owner so every inbound inquiry has a home.

Follow-up discipline

Due-dated tasks keep next actions visible instead of buried in personal notes.

Appointment basics

Schedule and review appointments linked to leads without expanding into full field dispatch.

Main modules

  • Leads
  • Follow-ups
  • Appointments
  • Users and roles
  • Tenant settings

Technology stack

Laravel · Next.js · MySQL · Redis

Architecture summary

  • Laravel modular monolith API
  • Next.js App Router frontend
  • MySQL as primary datastore
  • Redis for queues and cache
  • Tenant-scoped authorization on business entities

Security considerations

  • Authenticated sessions with server-side authorization
  • Tenant scoping on all business queries
  • Request validation on every write
  • Rate limiting on auth and public intake endpoints when exposed
  • Secrets kept in environment configuration

Interface gallery

BookedFlow — Lead and Appointment SaaSUnder Development
Development showcase mockup for an in-progress product. Temporary visual — will be replaced with a real product screenshot when ready. Sample data only.

Current phase

BookedFlow is an EH DESIGN SaaS product initiative at MVP stage and in active development. No production customer base or commercial results are claimed.

Scope boundaries

  • No Twilio, Stripe, AI, dispatch, invoicing or GPS in MVP scope
  • Not a full CRM or marketing automation suite
  • Not presented as a finished self-serve marketplace product
  • Integrations only when explicitly scoped later

Remaining work

  • Harden core MVP flows and empty states
  • Operator onboarding checklist
  • Additional appointment conflict rules
  • Staging readiness for early internal trials

Main workflows

Capture a lead

Record contact details, source and owner, then place the lead in an explicit status.

Plan follow-up

Create a due-dated follow-up task, complete or reschedule it and keep ownership visible.

Book an appointment

Convert a qualified lead into an appointment within the agreed availability rules.

Review the day

Managers scan open leads, overdue follow-ups and today’s appointments in one operational view.

Technical decisions

Protect MVP scope

Lead, follow-up and appointment excellence comes before payments, messaging gateways or automation platforms.

Laravel + Next.js split

Clear API ownership keeps authorization and validation off the client while the UI stays conversion-focused.

Tenant isolation early

Business data scoped by tenant from day one avoids a painful retrofit later.

Redis only where justified

Queues and cache use Redis; no speculative microservices.

Testing approach

  • Feature tests for lead, follow-up and appointment flows
  • Authorization tests denying cross-tenant access
  • Validation tests for required intake fields
  • Manual UX passes on empty and error states

Related work

CMDS — Commercial Desktop ERP
Commercial Desktop ERPWindows desktopRelease candidate

CMDS

Offline-first Windows desktop ERP for trading counters and branches — inventory, sales, purchasing, payments, expenses and reporting. Release Candidate v1.0.0.

  • Offline-first Windows counter operations
  • Sales, stock and treasury in one local record
  • Role-gated discounts and adjustments

Technology: .NET 8 · WPF · SQL Server · EF Core

EH Gym ERP — Gym Management Platform
Gym Management PlatformWebDevelopment / pilot preparation

EH Gym ERP

Web gym and fitness management for memberships, subscriptions, attendance, trainers, classes, POS, finance and reports. Preparing for pilot use.

  • Membership and subscription periods
  • Attendance and class scheduling
  • POS linked to member accounts

Technology: ASP.NET Core 8 · Next.js 15 · SQL Server · EF Core

Let’s Build a Better Business System.

Tell us about your workflow, operational challenge or product idea. We will review the requirements and discuss a practical next step.