Book a free systems audit (opens the booking page in a new tab)

The garageWhat we do and who it is for

Your tools do not talk. We complete the circuit.

Durham, NC · Systems integration, data automation, and custom builds

We run the systems side, on contract, for companies under a hundred people.

  • Your tools do not talk to each other.
  • Your numbers live in three places that disagree.
  • Someone re-exports the same report by hand every week.
Book a free 45-minute systems audit (opens the booking page in a new tab)

No charge, and you keep the map either way. Prefer email? Email us

Services

Mod list

Powertrain

Systems integration

We connect systems that were never built to talk to each other and prove the numbers reconcile.

Electronics and data

Data automation

We pull records out of systems that were never designed to give them up and make the result trustworthy enough to run a business on.

Aero

Custom builds

When off-the-shelf software will not do the job, we build the piece that does: dashboards, storefront features and internal tools.

Mod list

Powertrain

Systems integration

We connect systems that were never built to talk to each other and prove the numbers reconcile.

  • Integrations between systems with no shared key
  • A nightly sync normalizing every sale into one schema behind an idempotent line key
  • Integration of an un-integrable system through bulk-upload spreadsheets generated against its exact template contract
5 platforms bridged
The limit

When a platform changes how it identifies records, existing mappings break and have to be rederived. That is a recurring cost, not a one-time setup, and we price it as one.

Electronics and data

Data automation

We pull records out of systems that were never designed to give them up and make the result trustworthy enough to run a business on.

  • Data extraction and cleaning
  • Automated inventory agents
  • Scheduled jobs that reconcile stock across storefronts sharing one warehouse
153 mornings scheduled, 142 completed unattended
The limit

Cleaning can surface and flag bad source data; it cannot invent data that was never captured. Where a value is missing, the system says so rather than guessing.

Aero

Custom builds

When off-the-shelf software will not do the job, we build the piece that does: dashboards, storefront features and internal tools.

  • Operator-facing dashboards
  • Custom storefronts and commerce logic
  • A bundle and minimum-order-quantity builder that handles parent, variant, and standalone products
2 custom builds live on one wholesale channel
The limit

A storefront reflects the catalog it is given. Bundle and stock logic can only be as right as the product data underneath it, so on a messy catalog the data work comes first, and the audit says so before you build.

Live systems

Telemetry

Here is a sample running right now, measured honestly, not the ceiling of what we can build.

Live systems
SystemScheduleRuns completed unattendedStatus
Warehouse inventory agentEvery morning since May 8142 of 153Running
Multi-channel revenue syncEvery day since June 17100 of 112Running
Weekly profit summaryEvery week since August 310 of 10Running
No-API inventory bridgeNot scheduled329 tests, offlineShipped

Counted from the run history on October 7, 2026. Self-reported, verifiable on request.

Case studies

Dyno sheets

Every system below was built, and is still run, in an operations role at a single multi-brand retail and wholesale group: end-to-end systems work shown in depth, not a wall of logos. The group is described by architecture, not by name; every figure measures the systems, never its business.

Self-reported, verifiable on request

Ten locations, three platforms, one defensible number

Built by Madison Clore · Operations role

18,626rows independently recomputed from scratch and reconciled to the cent
Problem
Three e-commerce storefronts and two mutually incompatible point-of-sale systems spanned roughly ten locations.
Approach
A nightly sync normalized every sale into one schema behind an idempotent line key.
Full report
Problem
Three e-commerce storefronts and two mutually incompatible point-of-sale systems spanned roughly ten locations. Manual cost corrections were destroyed on every rerun, so the same reconciliation work restarted from zero each session.
Approach
A nightly sync normalized every sale into one schema behind an idempotent line key, with a write contract that updated only volatile fields, so operator-owned columns survived automation.

18,626 rows were independently recomputed from scratch and reconciled to the cent across all 18 store-month buckets.

Caught and corrected · Spurious record creates, per run

  • ~2,000Out of bounds
  • ~40In bounds

A silent 10,000-row platform query ceiling was double-counting records before it was found. Spurious creates ran near 2,000 per run until the chunking strategy was rewritten, and now sit at about 40. The ceiling was the platform's; the few weeks it took to detect were the build's, and the reconciliation audit exists so the next one surfaces in a day.

Three storefronts, one warehouse, one number

Built by Madison Clore · Operations role

76 to 11 minDaily reconciliation runtime
Problem
Three storefronts drew on a single physical warehouse, each holding its own idea of stock.
Approach
Scheduled jobs reconciled stock across storefronts sharing one warehouse.
Full report
Problem
Three storefronts drew on a single physical warehouse, each holding its own idea of stock. Reorder and deadstock decisions were being made from spreadsheets that were stale before they were opened.
Approach
A morning reconciliation built a single per-SKU source of truth, computed reorder, deadstock, stockout, and backorder decisions, and delivered them into the tools the team already used rather than a new one to learn.

Daily reconciliation was cut from about 76 minutes to about 11, on 142 of 153 scheduled daily runs since May 8.

  • ~76 minOut of bounds
  • ~11 minIn bounds

That 7x was this workload's headroom, not a promise. Once the obvious waste is gone, the next gains cost far more for far less, and a job that already finishes comfortably inside its window is not worth optimizing further. We will tell you when you have hit that point rather than bill past it.

No API, no problem

Built by Madison Clore · Operations role

329Tests passing offlineShipped
Problem
The inventory system of record had no API.
Approach
The build integrated the un-integrable system by generating bulk-upload spreadsheets against its exact template contract.
Full report
Problem
The inventory system of record had no API. None. Every new product had to be hand-entered there and then re-entered across three storefronts.
Approach
The build integrated the un-integrable system by generating bulk-upload spreadsheets against its exact template contract, driven from a single structured row. One row in, three storefronts out.

One structured row produces a launch across three storefronts, proven by 329 tests that run fully offline in about 15 seconds.

A spreadsheet contract is a brittle integration by definition. It breaks the day the vendor changes their template. That is exactly why the whole suite runs offline against a pinned contract: the break surfaces in CI, before production, not after.

Two custom builds on one wholesale channel

Built by Madison Clore · Operations role

Order minimums the platform could not enforce

3Bundle types handledparent, variant, standalone
Problem
The wholesale storefront ran on BigCommerce, but the business sold in mixed bundles, each with minimum order quantities the platform had no native way to enforce.
Approach
A bundle and minimum-order-quantity builder handled parent, variant, and standalone products.
Full report
Problem
The wholesale storefront ran on BigCommerce, but the business sold in mixed bundles, each with minimum order quantities the platform had no native way to enforce. Policing it by hand, order by order, did not scale.
Approach
A custom Stencil storefront had a bundle engine built into the product page and the cart: parent bundles, variant bundles, and standalone products, each carrying its own minimum-order rule, enforced before checkout instead of caught after.

Custom minimum-order and bundle rules were enforced at the buy button, on a platform that had no way to enforce them before.

The rules are enforced where the order is placed: in the storefront. An order taken another way, over the phone or keyed in by hand, does not pass through them, so the wholesale policy has to be owned in one place rather than reapplied per channel.

An application that files itself.

Built in 2 days160 tests
Problem
Wholesale account applications arrived by email and phone, with the paperwork chased by hand and nothing tracked.
Approach
A public form that checks each application for spam, files the uploads and a one-page summary in the company's own drive, adds a row to the tracking sheet the reviewer already uses, and alerts the reviewer, with every submission only ever adding a row so the reviewer's own edits are never overwritten.
Full report

A form files and alerts; it does not approve anyone. The review is still a person's judgment, and the spam check and upload limits are the kind of thing that needs a look every few months as the tools around them change.

How we work

Build plan

Stage 1 of 4

Systems audit

What happens: A 45-minute call, no charge. We walk your systems together and trace how your data actually moves and where it stalls.

Stage 2 of 4

Scoped plan

What happens: We turn that map into a fixed scope with the price already on it. You read it and approve it before any code is written.

Stage 3 of 4

The build

What happens: We write the code in a repository you own, on scoped credentials you create in your own accounts and can switch off yourself. None of it runs on our infrastructure.

Stage 4 of 4

Runbook handoff

What happens: We hand over a runbook written during the build, not reconstructed at the end. You keep running the systems yourself, or hand them to any developer you choose.

Build plan

Four stages, every engagement, in the same order. Each one ends with a document or a working system in your hands, not a promise for later.

What you keep

  1. 01Systems auditA written data-flow map and the three automations in it worth the most to you. Yours to keep, hire us or not.
  2. 02Scoped planA fixed scope and a fixed price, in writing and in your hands before the first commit.
  3. 03The buildWorking systems in a repository you own, with the tests and commit history that show they do what we said.
  4. 04Runbook handoffThe runbook, written into the repository you already own. Nothing runs on our machines, so nothing leaves with us.

    The last handoff shipped as a full-store snapshot: every product, image and the storefront theme, as spreadsheets and a readable image tree, with a restore tool, so the backup is insurance rather than a record.

    The limit

    The stages are the order every engagement runs in, not a promise of what each one finds. A 45-minute audit maps only what 45 minutes can reach, and a scope is an estimate written before the first line of code. When the build turns up something neither of them caught, you see it in the same repository, priced the same way, before we act on it.

Spec sheetRates & terms

The contract, stated plainly

From $2,500

$2,500

Most first builds start around $2,500.

$5,000
$15,000

A typical engagement lands between $5,000 and $15,000.

Larger phased programs are quoted the same way.

Engagement

Fixed-scope builds, or ongoing support on a monthly retainer, month-to-month with 30 days' notice.

Systems audit

45 minutes, no charge. You get a written map of your data flows and the three highest-value automations available to you, whether or not you hire us.

Book a free 45-minute systems audit (opens the booking page in a new tab)

The crewWho does the work

The person who scopes your build is the person who builds it.

  • Madison Clore, founder of Maddock Circuit Systems
    Founder · systems engineer

    Durham, NC · Systems integration, data automation, and custom builds

    I am Madison Clore, VP of Systems & Operations by day, which is where the production systems on this page were built and where they still run. Maddock Circuit Systems is how I take that same work on directly.

    Your engagement is separate from that role: it runs on your own systems under scoped credentials you control, and carries no prior-employer code or IP. The systems above are shown by architecture, as proof of capability, not reused.

    I take on work around that day role, which is why the crew keeps its engagements few.

    LinkedIn profile (opens in a new tab)

We take on a small number of engagements at a time, so there is sometimes a wait before we can start. If your timeline cannot move, we are the wrong choice, and we would rather tell you that early than take the work and stretch it thin.

Tech inspectionFAQs

The questions a careful buyer asks before hiring a small, independent firm. Each answer carries its limit, the same as everything else here.

Small and mid-sized businesses, usually under a hundred people. That is the stage where a company has outgrown spreadsheets and hand-keyed reports but cannot yet justify a full-time systems or data team. If your tools do not talk to each other, your numbers live in three places that disagree, someone re-exports the same report by hand every week, or off-the-shelf software will not quite do what your business needs, that is the work. The industry matters far less than the shape of the problem.

Both ends of the range are the wrong fit. A company with no core tools chosen yet is better off picking those first, because we connect and automate the systems you already run; we do not choose your CRM for you. A large enterprise with its own data team and procurement is more than a practice this size takes on today. The fit is the stretch in between.

Video coming soon

Contact

Shakedown

A 45-minute systems audit costs nothing, and you keep the map either way.

Book a free 45-minute systems audit (opens the booking page in a new tab)

Prefer email? Write contact@maddockcircuitsystems.com.

Replies within 1 to 3 business days

Durham, NC