Data & Enterprise Consulting
I get complicated things working.
Organizations bring me the problems that don't have an obvious owner yet — data at scale, the infrastructure underneath it, and the compliance questions everyone else routed around.
Currently taking a small number of engagements
Clean data, sound systems, decisions that hold.
DATA OPERATIONS
Large consumer and business files — cleaned, completed, and made reachable again.
INFRASTRUCTURE & SYSTEMS
The systems an organization actually runs on, including the ones nobody owns yet.
COMPLIANCE & CONSENT
Consent captured with proof, lists screened before anyone dials, records you can produce.
The method
How the work runs
One continuous operation in two halves that close into a loop. Rest on a step to read it.
Getting to them
I clean the file.
Every record checked against national address data, duplicates merged, and people who have passed away quietly removed. You stop paying to reach people who are not there.
What comes back
Getting to them
What comes back
I clean the file.
Every record checked against national address data, duplicates merged, and people who have passed away quietly removed. You stop paying to reach people who are not there.
What worked feeds back in. Every response teaches me something about who actually converts, and that sharpens the next audience instead of starting over.
Most people start at step four and wonder why it isn't working.
Situations I get called about
You might recognize your week here
Businesses selling to consumers
The audience built on a dead list
You're running ads against an audience modeled on a customer file you last touched years ago. A large share of those records are stale — wrong numbers, changed emails, people who moved. The ad platform doesn't tell you that; it just spends the budget. I clean and complete the file before it ever becomes an audience, then model the audience from records that are actually current. The same budget now goes toward people who exist and can be reached, and nothing about your creative had to change.
The lead that went cold in an afternoon
A lead comes in at two o'clock. Someone picks it up at four. By then they've filled out three other forms and spoken to two of your competitors. I route leads to whoever is available the moment they arrive — by territory, by hours, by whatever rule fits how you actually staff. You call while you're still the only one who called.
The letter from a lawyer
A demand letter arrives about a text you sent eight months ago. You don't know where that number came from, whether the person opted in, or who to ask. I capture every submission with a time-stamped record of when and how that person agreed to be contacted, and screen the file against do-not-call lists before anyone dials. You produce the record, and the conversation ends there.
If any of that sounds like your month, tell me what you're working with. →
Working together
How engagements work
We talk first. A short conversation about what you're working with and what's actually going wrong. No deck, no discovery fee.
I scope it in writing. You get a written scope covering what I'll do, what it depends on, and what it costs. Fixed where it can be fixed.
Then we start. Your work gets attention rather than a queue position — that's the point of keeping the calendar short.
Contact
Start a conversation
Dane's front office. Sales, client services, biz dev — one line, no runaround. Tell me what you want.
Or send it straight through. Tell me what you're working with — I read these myself.
Every step of this work has rules attached. Updating addresses is a postal requirement. Removing the deceased before a mailing is basic decency. Calling and texting people carries consent obligations with real teeth, and identifying website visitors carries disclosure obligations of its own. Most operators skip that part because skipping is faster and nobody checks until something goes wrong. I don't — and when someone finally asks, I can show them exactly what happened and when.
I don't publish a client list.
What I am, and what I'm not.
I'm not an attorney. Nothing here is legal advice, and I don't offer opinions on what the law requires. Be careful with anyone in this industry who does.
What I have is a compliance function built on standing relationships with counsel who operate at the level of entire industries — the lawyers that recognized brands call before they launch, not after something goes wrong. Every legal question that comes out of an engagement goes to them, and the answer comes back in writing. Then I build to it.
It means I'm slower than the people who will tell you it's probably fine. It also means you're not relying on a vendor's guess about your exposure.
Messaging compliance
Your texts aren't arriving, and nobody told you.
There are two separate ways a messaging program goes wrong, and most people only find out about either one after the money is spent. The carriers can quietly filter your traffic because your registration doesn't match what you're actually sending. Or you can text someone who never properly agreed to hear from you, and the penalties there run per message.
I handle both before the first send.
Getting your messages delivered. Before any program starts, the sending brand and each individual campaign have to be registered with the carriers — this is what the industry calls 10DLC registration for A2P messaging, meaning business-to-consumer texting from a normal ten-digit number. What trips most people up isn't the registration itself; it's that the use case they declared doesn't match the messages they actually send, or the opt-in wording on their form doesn't match what's on file. Carriers check. When it doesn't line up they filter the traffic silently, and a delivery report can look perfectly healthy while a large share of the messages never landed.
Proving consent. Under the federal rules governing calls and texts — the TCPA — you need to be able to show that each person agreed to be contacted, in the right way, before you contacted them. Inheriting a list is not consent. A checkbox nobody can produce a record of is not consent. I capture consent at the point of collection with a time-stamped record of exactly what the person saw and agreed to, and I keep it in a form you can hand to someone.
Keeping the file clean. Before anything sends, the list gets checked against do-not-call registries, against known bad actors, and against people who make a living bringing claims over unwanted messages. That last check costs almost nothing and prevents the expensive kind of problem.
This is unglamorous work and most vendors skip it, because skipping it is faster and nothing happens until something does.
The messages that never arrived
You send a text program to your whole file. The delivery report looks fine. Almost nobody replies, nothing bounced, and you spend a week wondering whether your message was wrong. I register the sending brand and each campaign properly, and make sure the use case on file matches what you're actually sending. Your messages arrive, and the response rate you were expecting shows up.
Shut off on day four
Your number stops sending partway through a program. No warning, no explanation, and getting it turned back on means restarting a registration you were told was already handled. I get the registration right before the first send and keep the opt-in wording on your form matching what's filed with the carriers. The program runs the whole way through.
The letter about a text
Somebody complains about a message you sent months ago. Then a letter arrives asking you to produce proof that the person agreed to be contacted, on a list you inherited from a vendor who is no longer returning calls. I capture consent at the point of collection with a time-stamped record, and screen the file before anything goes out. You produce the record, and it stops there.
The campaign that couldn't launch
Your messaging vendor asks for consent documentation on the file you handed them. You don't have it in a form they'll accept, launch slides, and the window you were targeting closes. I handle registration and consent documentation before the file ever reaches a vendor. You launch on the date you planned.
If your messages stopped arriving and nobody can tell you why, tell me what you're working with. →
Before anything goes out
The questions I ask first
Which rules apply to you depends on what you're doing, where the people live, and what you plan to do with the answer.
That last one catches the most people. Using data to decide who gets an offer is marketing. Using the same data to decide who gets approved is a different body of law entirely, and it arrives with obligations most vendors never mention — usually because they don't know either.
Financial services and health data each carry their own federal regimes on top of everything above.
Campaigns and committees answer to election regulators as well as consumer ones.
Charities answer to the states they solicit in, and to the limits attached to their own tax status.
Most people don't have all of these. Working out which ones you do have — and which ones you have because of something you did two years ago — is most of the job. When one of them needs a legal opinion, it goes to counsel and comes back in writing, the way everything here does.
If three of those questions made you pause, tell me what you're working with. →