Flagship Product · Functional Platform · Deployment Pending
A multi-tenant CRM and growth platform designed for agencies and businesses that need one connected system for leads, pipelines, appointments, automation, websites, AI chatbots and client operations.
The Problem
Lead capture, opportunity management, appointments, client access, websites, forms and follow-up often live in separate systems. That fragmentation creates duplicated work, unclear ownership and weak visibility across the customer journey.
LeadsTrackr is being built as an operating system for those connected workflows—not simply another contact database. The product gives an agency one platform while preserving clean boundaries between its own team, each client workspace and LeadsTrackr’s platform administration.
A Foundational Product Decision
The product uses three distinct operating layers. LeadsTrackr platform staff administer the SaaS itself. Agencies manage their teams and client portfolio. Sub-accounts isolate the day-to-day customer data and workflows belonging to each client or business location.
Why This Matters
Platform administration is not modelled as a special agency. That keeps ownership, support access, billing responsibilities and future capability-based permissions from leaking into customer workspaces.
Platform staff, agency oversight, support context and future commercial administration.
Agency owners, teams, shared operations, snapshots and access to multiple client workspaces.
Isolated leads, pipelines, appointments, automations, forms, websites, chatbots and customer activity.
01 · ACCOUNT SYSTEM
Agency accounts, client sub-accounts, owner memberships, scoped access, workspace switching and a separate platform-administration context.
02 · CRM
Connected records for leads, opportunities, pipeline stages, appointments, tasks, notes, activity and conversation history.
03 · AUTOMATION
Trigger, wait, condition and action nodes with branching, execution logs and the ability to test a workflow against a selected lead.
04 · DIGITAL EXPERIENCES
A structural visual builder with sections, rows, columns and elements, responsive controls, multi-page navigation and public publishing.
05 · PLATFORM
Public registration creates the user, agency, owner membership and first sub-account while platform staff retain a separate oversight area.
06 · PRODUCT EXPERIENCE
Clean public URLs, canonical metadata, responsive inheritance, publishing validation, accessibility improvements and regression tests.
07 · AI WEBSITE CHATBOTS
Configurable AI agents and publishable website widgets scoped to the correct sub-account, with instructions, knowledge, welcome messaging and autopilot or handoff response modes.
08 · CONVERSATIONS
Persistent conversations and messages preserve website-chat context, connect activity to the correct workspace and can associate a visitor with an existing or newly captured CRM lead.
From Website Visitor to CRM Context
I built an AI website-chat system inside LeadsTrackr so each sub-account can configure its own agent and widget while conversations remain attached to the correct workspace, lead and activity history.
Widget embeds have already been added to the LeadsTrackr marketing website and CaryWood.co. Public conversations will activate once the Rails application is deployed to a production host.
The published widget is installed on LeadsTrackr and CaryWood.co.
Instructions, knowledge, response mode and widget messaging stay workspace-specific.
Persistent records preserve status, timing and the complete webchat exchange.
Chat activity can connect with the CRM lead record and operational timeline.
Account boundaries, membership and permissions were built into the foundation so new modules do not have to retrofit customer isolation later.
Each sprint moves one capability from data model to authorization, interface, browser verification and automated tests before expanding scope.
LeadsTrackr’s own staff and permissions belong to the SaaS platform, not inside a pretend agency account. This leaves room for support, finance, sales and developer capabilities later.
End-to-End Ownership
LeadsTrackr began from operational problems I already understood through years of CRM, advertising, funnel and client-delivery work. I translated those workflows into the product model, interface and Rails implementation.
Technology
The stack prioritizes maintainability, relational clarity and focused JavaScript rather than unnecessary infrastructure complexity.
Development Practice
Work is split into testable checkpoints. Each batch includes explicit file changes, focused tests, browser validation, regression checks and a clean commit before the next product decision.
Functional Platform · Deployment Pending
LeadsTrackr already contains a connected CRM, automation engine, multi-tenant account structure, Sites platform and AI website-chat system. The Rails application currently runs locally, so the installed website widgets cannot serve public conversations until production deployment.
Deployment Status
The Heroku GitHub Student offer application is currently under review. Once hosting is available, the remaining work is production configuration, database setup, asset deployment and end-to-end verification of the embedded chat widgets on both websites.
Marketing website live · Rails application deployment pendingProduct Strategy · Architecture · Rails Development
Explore the rest of my software and client work, review my development profile or start a conversation about product engineering and growth systems.