Est. 2026 · Travelers Rest, SC

The infrastructure layer between you and everything you're trying to build.

Practical, durable systems for the way you actually work. No reseller margin. No demoware that doesn't survive Monday morning. Just operations infrastructure engineered around your reality - whether that's a mid-market business or one ambitious operator.

Start with a conversation See how I work
Discipline
Operations
infrastructure
Practice
Solo operator
+ 1099 bench
Capacity
Capped
by design
Posture
Pragmatic, durable,
accountable
02 / Two Tracks

One operator. Two operating contexts - built differently for each.

A business and a person are not the same problem. A team needs throughput, governance, and shared rails. An individual needs leverage, focus, and a system that thinks the way they do. I build for each on its own terms.

● Track 01 · Operations

For your business

Workflows, integrations, and the quiet automation that replaces the parts of your operation that bleed time. I come in, watch the operation, and rebuild the friction points.

  • .01Workflow automationQuoting, intake, reporting, handoffs - the daily friction.
  • .02Data pipelines & integrationYour systems, talking to each other, with a memory.
  • .03Decision & copilot toolingModern tools your team will actually use after week two.
  • .04Governance & observabilityYou can see what the system did and why.
Engagement options → SMB · Mid-market
● Track 02 · Personal OS

For you, personally

A personal operating system designed around your actual day - capture, decisions, follow-through, and the leverage to compound. Not someone else's productivity religion.

  • .01Daily operating systemInputs, queues, decisions, follow-through - one architecture.
  • .02Knowledge infrastructureCapture once. Retrieve forever. Build on top of it.
  • .03Thinking & writing systemsDrafts, decisions, and dialogue with your own archive.
  • .04Calm operating postureLess app-fatigue. More leverage. Quieter weeks.
Engagement options → Founders & high-output operators
03 / Field-tested

I don't pitch infrastructure. I operate on it.

Every pattern I ship - daily operating systems, knowledge pipelines, decision tooling - runs in production for me first. These are the systems I built for myself and use every day.

Meridian Portfolio01

Crucible

Personal OS

Daily operating system. Brief, body, capture, menu - one architecture for how an operator actually runs a day.

In production
Meridian Portfolio02

Chaos

Trading Intelligence

Swing-trade screener and signals engine. Multi-setup framework, batch analysis, structured daily brief.

In production
Meridian Portfolio03

Quill

Capture & Task System

Lightweight task and capture layer designed to live where the work happens - not in another app you stop opening.

Beta
Meridian Portfolio04

Forge

Training Program Engine

PDF-to-progressive-overload tracker. Turns any structured program into a running, adjustable system.

In development
04 / How it works

Three phases. One throughline: systems that hold up.

No 90-page decks. No theatrical kickoffs. A short observation period, a build phase scoped to what's actually important, and a long tail of operating it with you so the thing keeps working when no one is watching.

01Discover

Observe before prescribing.

I sit alongside your operation - or your week - and map the real flow. Where time leaks, where decisions stall, where a system would change the math. No tool selection on day one.

Operator interviews & shadowing System & data inventory Friction map & opportunity brief
02Build

Scoped, durable, yours.

A focused build phase against a written spec. I pick boring, durable foundations - not the thing that was viral last week. You own the artifacts, the prompts, the data, the integrations.

Architecture & written spec Iterative builds with weekly demos Evals, fallbacks, observability
03Operate

Run it. Refine it. Hand it off.

Most infrastructure projects fail in the third month. I stay through it. Adoption support, tuning, monitoring, and a clear off-ramp when your team is ready to drive without me in the passenger seat.

Adoption & team enablement Monthly tuning & review Documented handoff & runbooks
05 / Why Meridian

Built by an operator, for the way work actually happens.

Meridian is not a venture-backed platform. Not a reseller. A small, deliberate practice that builds operations infrastructure for clients I can sit across the table from.

Principal

David Erickson II

Founder · CMA

Fourteen years inside founder-led businesses - operations, finance, turnaround. CMA. Scaled an accounting function through a 4.5× revenue jump with roughly 1.5× headcount - leverage that only comes from replacing process with system. Currently still in the operator's seat at scale; Meridian is the practice built from that toolset. I bring in trusted hourly help where it sharpens the build; the work stays accountable to one person.

.01

Operator-first lens.

Every system I ship has to survive a real Tuesday. I design for the person at the keyboard, the team at the standup, the founder at 6am - not a slide.

.02

Upstate SC roots, regional focus.

Headquartered in Travelers Rest with a working radius across the Upstate. I meet in person, I know your industry, and I'm accountable to people who can find me at lunch.

.03

I use what I ship.

Every workflow, every personal OS pattern, every pipeline - I run versions of it myself, every day. If it doesn't work for me, it doesn't make it to your build.

.04

Durable over flashy.

I pick the boring foundation that will still be here in 18 months. Vendor-portable, well-documented, observable. Less ceremony, more compounding.

.05

Transparent engagement.

You will know what I am doing, what it costs, and what you own at the end. Three engagement shapes; no surprise invoices; clean off-ramps.

06 / Engagement Model

Three shapes. Pick the one that matches the problem.

No mystery pricing pages, no "contact for quote" theatre, no ten-page MSAs. Three transparent engagement structures, scoped to fit how your work actually arrives. I'll tell you which one fits in the first conversation.

07 / Start a conversation

The first conversation is just a conversation.

Tell me a little about the operation, the person, or the problem. I'll come back within two business days with whether I'm the right fit, and what a sensible first step looks like. No pitch deck. No pressure.

Based in
Travelers Rest, South Carolina
Working radius
Upstate SC · Charlotte · Atlanta · Remote
Response time
Within 2 business days

Tell me about it.

Inquiry
Required
Enter a valid email
A sentence or two is plenty

Received.

Thanks - I'll come back to you within two business days. If it's urgent, email david@meridiantechco.com directly.