$15,000 of free development.
Your bottleneck, solved in a week. No $ upfront.
20+ years as a senior engineer & project architect.
Air Force Captain. Physicist. CTO. DeFi banking, AI, tech.
Very limited project capacity.
The Free Week.
Exactly what it is.
To start the free week, on the 15-min call we lock three things.
What “shipped by Friday” actually looks like.
Four real examples. Clients under NDA — references available on the call.
Your inbox, mostly handled.
You read 200 emails a week. Most are noise — vendor pings, the same five customer questions, status updates. By Friday you’ve got an agent that drafts replies to the routine 90% and only surfaces the ones that need you. Conservative: six hours a week, back.
Cancel the $4K/year SaaS.
That tool you renew every January that does one thing your team actually uses? By Friday that one thing lives in your stack. You stop paying. The data stays yours. The renewal email never lands.
Two systems, finally talking.
Your sales platform doesn’t talk to your fulfillment system, so someone copies between them three times a day. By Friday they sync — automatically, with audit logs. That someone gets their Tuesday back.
Tier-1 support, on autopilot.
The five questions your support team answers 80% of the time? An agent handles them in your voice, escalates the weird ones to you, and learns from your corrections. Customers get answers in 30 seconds instead of 30 hours.
Twenty years bylding.
No logo wall — most engagements are under NDA. Below: a few I can name.
The Friday Guarantee.
You’ve got working code and you want me to keep going → we talk retainer.
You’ve got working code but want to take it from here → keep it. No invoice.
I didn’t ship what we agreed on → you still keep the code. I cover one referral call to a peer who fits better.
Heads you win, tails you also win.
Questions you’d ask if we were on a call.
> q: Are you a fractional CTO?
No. Fractional CTOs advise and never open PRs. I write the code, review yours, and ship in your repo on Friday. The senior-architect framing only works if the senior architect is the one writing the code.
> q: How is “free week” not a sales gimmick?
Because the deliverable is locked before I start, and you keep the code regardless of what happens Friday. The week filters for clients I want to work with. If I’m wrong about the fit, I eat the cost, you keep the code, and I refer you to a peer.
> q: What if I’m not technical enough to know what to ship?
Then we use the 15-min call to find one. I’ve done this enough that the bottleneck is usually obvious within ten minutes. If it isn’t, that’s a signal we shouldn’t start the week yet.
> q: Do you have a team or is it just you?
It’s me. If a project needs a team, I tell you on the call and I will enlist trusted peers to assist.
> q: What’s your stack?
Python, TypeScript, Postgres, AWS/GCP. Comfortable in Go and Rust where the problem rewards it. AI: Claude, OpenAI, vector DBs, tool-use frameworks. Crypto: EVM, USDC rails, custody patterns.
> q: Why not just hire a full-time senior?
$200K + benefits + 90-day search + ramp. If you can justify that, you should hire. If you can’t, retainer is the only way to get senior thinking on the cap table without owning it.
> q: How is this different from an agency?
An agency sells you a project manager and three juniors. I sell you me, writing in your repo, Friday morning. No PM layer. No status meetings. No SOW negotiation.
> q: Why byldr?
I like the name. I think it looks cool.
> q: What about NDAs?
Happy to sign one if you need it.
> q: Do you do equity-for-build?
No. Equity dilutes the senior-architect framing into co-founder territory and changes the conversation. Cash retainers only.
> q: What if I want to pause / restart?
One-month notice on the retainer side, prorated. No long contracts. The retainer holds because the work’s good, not because the paperwork traps you.