Andrew Tabb Get in touch

Andrew Tabb

Technical support, implementation and onboarding, product analytics · Raleigh, NC

Over a thousand remote customer engagements. Products that are live, hosted, and supported.

See experience See live products

Experience

Late 2021 to present

Owner and Operator, Remote Technical Services Business

Raleigh, NC

Late 2021 to present
Full time since early 2023

Built and operate a remote technical services business serving customers across three continents, reached and supported through Discord communities.

  • Grew the business from a part-time start in late 2021 to full time by early 2023; over a thousand completed client engagements, driven by repeat and long-term customer relationships.
  • Implement each customer's setup remotely on Parsec: onboard non-technical customers onto the software, give platform-specific configuration guidance for Windows and macOS, import the working profile, and validate settings against a required spec before work begins.
  • Run the full support workflow: intake, ticket logging, completion-evidence capture, and per-engagement records, maintained in own logs and spreadsheets.
  • Built the environment a network of independent providers delivers through: authored the operating procedures and standards the work is delivered against, hold the customer relationships, match skilled providers to customer engagements, and handle the commercial side of each.
  • Price work against multiple market reference sources; coordinate payment on multi-party transactions.
  • Support staff on one Discord community; founder and operator of a second.

Founder, Tabb Labs LLC

Raleigh, NC

2026 to present

Independent software studio. Owns design, delivery, hosting, releases, and support for its products.

  • StudyRoster (studyroster.com): scheduling, reminders, invoicing, and session notes for independent tutors. Live on the web and on Google Play as a native Android app; subscription model with a free trial. Self-hosted; production releases shipped through Google Play review.
  • Designed StudyRoster's feature-usage telemetry: fixed event keys and IDs only, no personal data by construction.
  • Hell Swarm (hellswarm.net): browser game playtested by 25+ people. Player feedback is captured as structured data that sets the build priorities.
  • Designed and built two B2B operations applications: DiveWell (divewell.app), an operations platform for dive shops, deployed and live with signups closed; and TankBinder (tankbinder.com), UST compliance recordkeeping for fuel-tank operators in English and Spanish, built and tested with its product site live. Neither is open to customers yet.
  • Builds with AI development tooling (Claude Code) inside a verification system of own design: independent QA, security, and release checks must pass before any change ships.

Live products

2026 to present
Live
StudyRoster app screenshot
studyroster.com

StudyRoster

A study-tracking app. I built it, deploy it, and support it. Live on the web and on Google Play as a native Android app, with a free trial that converts to a subscription.

studyroster.com →
Live
Hell Swarm gameplay screenshot
HS
hellswarm.net

Hell Swarm

A browser game, playtested by 25+ people. Player input feeds structured data that shapes what I build next.

hellswarm.net →

Built

Not open to customers
Not open to customers
DW
divewell.app

DiveWell

An operations platform for dive shops: dive-native maintenance and compliance records, rentals, waivers. Designed, built, and deployed as a registered assumed business name (DBA) under Tabb Labs LLC. The application is live; signups are closed for now.

divewell.app →
Not open to customers
TB
tankbinder.com

TankBinder

UST compliance recordkeeping for fuel-tank operators, in English and Spanish. Designed and built as a registered assumed business name (DBA) under Tabb Labs LLC; the application is built and tested, and the product site is live at tankbinder.com. Not open to customers yet.

tankbinder.com →
Pendo, hands-on

Product analytics

2026

I learned Pendo by using it. Here is what I have done so far.

1

Instrumented a sandbox app with Pendo, end to end. Built a four-page web app ("Acme Tasks") for the purpose, installed the Pendo agent, verified with pendo.validateInstall(), tagged four pages and five features, and built a segment and an Add Task → Done funnel.

2

Used Novus end to end. Connected Novus to a scoped repo, reviewed and merged its SDK-install pull request, and built a product map. Novus is built on Anthropic's Claude, which I work in daily.

3

Earned the Pendo Admin Certification. Passed the certification exam on Pendo Academy.

Pendo Admin Certified badge
4

Designed StudyRoster's feature-usage telemetry: fixed event keys and IDs only, no personal data by construction.

Add Task → Done funnel (built in Pendo)
Visit app
Add Task
Task added
Done
How I work

The system I built to work this way

I built a system to keep myself consistent as a solo builder. It is not the product, it is how I work.

12+ projects 30+ specialist agents 40+ automated guards 3 independent review gates 6 layers
1Governance

A written rulebook every session inherits: how to work, what not to touch, when to stop.

Shared disciplines Coined shared vocabulary Decision log with the reasoning Per-project charters
2Enforcement

Automated guards that check each action before it runs, so the rules hold under pressure.

Pre-action permission checks Sensitive-data containment Tamper-evident control layer Recoverable-only deletion
3Specialist agents

A fleet of focused agents, each with one job and clear limits, plus independent reviewers that check the work before I see it.

Lane-scoped specialists Independent review gates A quality critic A reviewer that predicts my verdict before I see the work
4Memory

Everything learned is written down and kept, so the system improves instead of forgetting.

Per-agent memory Rollups (daily to weekly to monthly) Search across all projects' history Preserve-only, never deleted
5Routing

Projects hand work to each other through structured messages, never by reaching into each other's files.

Every project has an inbox Work-orders, not direct edits Cross-project requests Symmetric replies
6Lifecycle

Every session starts and ends the same way: orient, work inside the rails, log everything, then I review and approve.

Startup pre-flight Work inside the rails Closeout logging and self-review I review and approve
Self-improvement loop
Failure caught Written down Mechanism fixed New automatic guard Applies everywhere
Cross-project work
Needs out-of-lane work Work-order to another project's inbox Swept at startup Done in-lane Reply to sender
Review before I see it
Build QA Security Release I review and approve
Layer Sub-node Review gate Flow / connector
What I do

Skills and stack

  • CustomerTechnical support for non-technical users · Customer onboarding and enablement · Remote support on Parsec · Community-based support (Discord) · Troubleshooting across Windows and macOS
  • ProductProduct analytics (Pendo, certified) · Feature tagging, segments, and funnels · Feedback to roadmap · Full-lifecycle product ownership
  • OperationsWritten operating procedures and standards · Ticket and records management · Provider network: standards, matching, and payment coordination · Pricing analysis
  • TechnicalAI-assisted development (Claude Code) · Deployment and self-hosting · Google Play release management · Web and mobile app delivery

Resume

One-page resume (PDF) · updated September 2026 Download resume (PDF)
Page one of Andrew Tabb's resume View resume (PDF)

Get in touch

One inbox reaches me directly.

[email protected]
LinkedIn studyroster.com hellswarm.net