White-label delivery
When work lands that your team cannot absorb, the usual choices are to turn it down or to let something else slip. I take the part that is slipping: data cleanup, SQL and database work, dashboards, and reporting. It goes out under your name.
$85/hour · Fully remote, United States · Currently taking new overflow work
The situation
A good project lands. The client is one you want to keep. But your people are committed for the next six weeks and the work is due in three. Turning it down costs you the project and, eventually, the account. Taking it costs you the delivery date on something else.
Hiring does not solve a three week problem, and agencies your size do not carry a bench, because a bench is what makes the arithmetic stop working.
That gap is the only thing I do. Not strategy, not a partnership, not a standing retainer. The specific piece of delivery that will not fit, taken off your plate and handed back finished with your name on it.
Scope
The second list matters more than the first. A subcontractor who says yes to everything is a subcontractor you have to check.
Engagement
Trying me should cost you one email and no risk. That is deliberate. You should not have to take my word for any of this.
What landed, when it is due, and roughly what the data looks like. No brief, no form, no discovery call. If it is not something I should be doing, I will tell you and point you somewhere better if I can. That answer costs you one email.
I sign yours. I do not send you mine and you do not have to negotiate a template before anything can start. Then a scope and a price, agreed before any work begins, rather than an hourly meter you have to supervise.
Your naming conventions, your folder structure, your template, your colours, your repo. The output should be indistinguishable from work your own team produced, because as far as the client is concerned that is what it is.
You hand it over. I am not on the call, not copied on the thread, not in the client’s contacts. It comes with handover notes written for whoever picks it up next, so you can answer questions in six months without coming back to me.
The obvious question
No, and here is the whole picture rather than the flattering half of it. I also take direct work under my own name: small businesses, mostly Microsoft 365 and reporting systems. That is a different market from yours and I keep it that way.
I do not approach agency clients. I do not accept direct work that reaches me through an agency engagement, during it or afterwards. If that matters to you, I will sign your non-solicit rather than send you mine, and I will sign it before the first task rather than after the third.
You are the client. The company whose logo is on the deliverable is yours.
Details
Something bounded and real, not a trial exercise. A dashboard page that needs rebuilding, a dataset that will not reconcile, a stored procedure that times out, a refresh that keeps failing. Small enough that if I am wrong about it, you have lost a few hours and not a client.
You hear that on day one, not day six. I would rather turn down a task than hand you something you have to check line by line before it can go out. That is why the list of what I do not take is as long as the list of what I do.
If it is my defect, I fix it and I do not bill for the fix. That is not a warranty policy, it is the only arrangement that makes sense. You cannot go back to your client and explain that the correction was extra.
Revisions inside the agreed scope are not extra. If the client changes what they want, that is a new scope and a new number, and you hear it as a question rather than see it on an invoice.
No. The person you brief is the person who does the work. Nothing is passed on, nothing is offshored, and no part of the job goes to anyone else.
Whatever you already use: email, your Slack or Teams as a guest, a shared board. I write a short note at the end of each working session so you are never wondering where something stands. I do not join client calls.
Yes, and it is usually cleaner than shipping files back and forth. Give me the narrowest access that lets me finish the task and revoke it when the task closes.
Yes. Handover notes, data dictionaries and runbooks come in your template with your name on them, or unbranded if you would rather add your own.
Evidence
Client work is under NDA or waiting on permission to publish. So all of this is public data I can show in full: method, code, and the results that went against me.
I find out that something does not work on my time and my budget, before it reaches your client.
Evaluated retrieval, NTSB public data
Question routing, a guarded SQL path, retrieval evaluation and an audit trail across 7,462 public aviation safety reports.
Limit
Hybrid retrieval did not clearly separate from simpler methods, so the product defaults to semantic search and exposes all three. The pilot set of 17 hand-labeled questions is too small to support a method choice.
Read the case study →Decision optimization, synthetic benchmark
Technician assignments under skills, capacity, deadlines, travel and overtime constraints, with both baselines and the optimizer built for comparison.
Limit
Synthetic data, not a production operation. The timed solver is nondeterministic, so the distribution matters more than any single scenario.
Read the case study →Statistical inference, public mortgage data
Five preregistered hypotheses on 41,287 curated applications drawn from 210,643 raw HMDA rows, with effect sizes, resampling and multiplicity controls.
Limit
HMDA lacks key underwriting variables. These findings are screening signals for deeper review, not discrimination findings.
Read the case study →Five more evaluated systems, including three where the result went against the build. View all eight and the evidence ledger →
Before any of it I ran the operations I was automating: a behavioral health practice of roughly twenty five people, covering staffing, payroll, billing, compliance, and the tracking systems that ran it day to day. Earlier I replaced paper and spreadsheet case tracking at a social services agency with database applications that real caseworkers actually adopted. That is the part that does not show up in a code sample, and it is why I ask what a report is for before I ask what it should look like.
There are no client logos on this page, and there is a reason. A subcontractor who will show you someone else's confidential work is telling you exactly what they will do with yours.
Commercials
Published, because you need to know whether I fit under your margin before you spend twenty minutes on a call.
No minimum, no retainer, and no charge for telling you a task is not worth doing. Defects in my own work are fixed without an invoice, because you cannot go back to your client and explain that the correction was extra.
Start
Not a brief, not a discovery call, not a capabilities deck. What landed and when it is due. If it is not something I should be doing, I will say so, and it has cost you one email.
Replies inside one business day. If I cannot take the work, you will know in that same reply rather than a week later.