Chris · analytics, funnels, storefronts

I build the tracking and funnel systems small brands are missing.

Ads, email, storefront and orders usually live in five different tabs and none of them agree. I connect them into one system that shows where revenue actually comes from, then build the pieces that fix the leaks.

Full e-commerce backend, fulfillment to finance
Storefronts designed to convert on a phone
Email automation with revenue attached
Funnel tracking you can actually trust
The problem

"Where did that sale come from?" should not be a guess.

Pixels say direct. The ad manager claims credit for everything. Email reports opens, not dollars. So decisions get made on vibes, and the budget goes to whatever felt like it worked.

The fix is not another dashboard. It is plumbing: first-party tracking that survives in-app browsers, attribution that falls back to the server when the browser loses the thread, and order data joined to the touchpoints that produced it.

orders · attribution
#1042 · express checkoutin-app browser
client pixel saiddirect
server first-touch resolvedfb / paid / campaign 52…59
evidenceproduct view minutes before purchase, same visitor
resultad credited · ROAS corrected
What I build

Revenue plumbing, not vanity dashboards.

Custom-built systems where every piece shares one source of truth. That is the structural advantage a stack of third-party apps can never give you.

01

Analytics & attribution systems

First-party tracking that follows a customer across visits and devices, attribution that corrects the orders platforms mislabel as "direct", and ad-platform reporting joined to real orders, so budget decisions run on evidence, not on the ad manager's self-grading.

first-party trackingtrue attributionad reportingcustomer journeys
02

Funnel infrastructure

Link-in-bio pages that know which platform sent every tap, branded short links with campaign tagging, and email automations (welcome, cart recovery, post-purchase) visualized as flowcharts with revenue on each step and copy you edit yourself. The boring parts that compound.

link trackingcampaign taggingemail flowscart recovery
03

Storefronts & ops tooling

Custom storefronts with every payment method your customers expect, and a management backend that makes fulfillment trivial: shipping labels bought from the order screen, pricing calculated automatically, finance tracked to a real per-order P&L instead of a spreadsheet.

custom storefrontsexpress checkoutfulfillmentfinance / P&L
04

Brand, landing pages & front-end

Logo and identity systems, conversion-focused landing pages, ad landers with popup capture, and product page design that respects how people actually shop on a phone inside Instagram.

identitylanding pagesad landersmobile-first
Selected work

Live products, not mockups.

Everything below is in production. Each page shows what it is, what it does in practice, and the edge it has over the off-the-shelf version.

How an engagement runs

Audit first. Build only what the numbers justify.

I do not start with a rebuild. I start by finding out what your current stack can and cannot tell you, and where money is leaking between the gaps. Then we fix the highest-leverage gap and measure it.

Pricing · one-time

The build

A scoped project fee for the system itself: storefront, backend, automation, tracking. You own the code and the data outright.

Pricing · monthly retainer

Keep it running, keep it growing

Ongoing maintenance, monitoring and troubleshooting, plus new features added as your business needs them. A standing engineer, without the payroll.

Funnel + data audit

Map every touchpoint from ad or post to paid order. Find what is untracked, double-counted, or simply wrong. You get a written report you can act on with or without me.

Instrument

First-party tracking, attribution fallbacks, UTM rules, catalog feeds, server events. Usually the biggest win for the least money.

Build the missing piece

Email flow, link system, landing page, storefront feature, or ops dashboard. Scoped to one outcome with a number attached.

Hand off, or stay on retainer

You own the code and the data either way. Dashboards you can read in two minutes, copy you can edit yourself, documentation that explains the why. Most clients keep me on a monthly retainer to maintain the system, fix whatever breaks, and build the next feature when the business asks for it.

Chris
About

One builder, whole stack.

I'm an electrical engineer by traditional education, and I currently run two e-commerce brands end to end, every piece custom-built: the storefronts customers see, the backend management system that ships the orders, the email automation, the review system, the analytics and the finance tracking. Nothing rented, nothing templated.

That's the credential that matters here: these systems aren't demos, they process real orders every day, and I'm the one who has to live with how well they work. When one person designs the front end, the data model and the automation together, the pieces agree with each other. Reports match reality, and nothing is a black box.

Direct communication, no account managers. You talk to the person who writes the code.

Storefront design + buildBackend management systemsEmail automationAnalytics + attributionFulfillment + shippingPayments + checkoutiOS appsBrand + identity
Contact

Tell me what you can't see yet.

Send a few lines about your business and what you are trying to figure out. I will reply within a day with honest thoughts on whether I can help, and a rough scope if I can.

Prefer email? chrus@realchrus.com