How I work
The Skylark posture isn’t a brand exercise. It’s a set of operating defaults I run by every day — small, concrete, mostly inherited from running a 100-person org and then unlearning most of what you do at scale when you go back to being one person again.
Here are the ones that actually shape the work.
Ship today, not tomorrow. If something is bounded — a fix, a small feature, a doc cleanup, a test — it ships in the session I noticed it. Carry-forward queues are friction; substrate that compounds is what makes a one-person studio actually work. The only acceptable reasons to defer: missing data, an upstream dependency, or something genuinely too large for a single session.
Read first, then build. Most teams ship faster than they read what they shipped. I’m running a 30-day posture right now where every project waits for the read at its next named decision gate before approving more substrate. “What does the data say?” before “what’s next?” That’s the binding constraint of a small studio — evidence volume at named decision points, not engineering throughput.
Cite primary sources. Flag uncertainty. Complicate your own claim. Three operating disciplines I picked up from years of internal memos and never let go. If I make a non-trivial factual claim, the citation is inline near the claim. If I’m not sure, I say “working theory” — never pretend certainty I don’t have. If I have a position, I’ll name the strongest argument against it before pushing forward. The dialectical move is what keeps reasoning honest.
Plain English, not jargon. Industry-standard acronyms stay. Internal shorthand translates. Decisions surface as “tomorrow’s two metric checks need a working DB connection” — not “B-004 blocks W-014.” If a phrase belongs on a LinkedIn slide, it’s already been cut.
Devil’s advocate is a feature, not optional. Every meaningful decision gets an argued-against pass. The point isn’t to look balanced — it’s to find the thing I’m systematically not seeing. Some of the best calls I’ve made this year are positions I held only because the first version of the counter-argument didn’t survive scrutiny.
Heartbeat over hope. If a process is long-running — a build, a deploy, a vendor outreach — I post a status update at 20-minute cadence. Silence isn’t a state; it’s just unobserved failure. This applies to everything: build outputs, partner reach-outs, my own progress on a hard problem.
Default Alive. Every Skylark project is a small profitable product designed to pay for itself, not a bet that needs Series A to survive. If you’re considering a Build Together engagement: the deal math has to work without acceleration. I’m not optimizing for a unicorn outcome. I’m building a beautiful portfolio studio that funds the life I want.
Calm tech. Attention is the scarce resource — not engagement metrics, not session length, not retention curves. Calm tech doesn’t mean low-stakes. It means respecting attention enough that a user is grateful when the product shows up. Anything we ship together has to pass the “would a smart reader feel they have to read this, or fall behind?” test. If not, the form is wrong.
What I won’t do. Founder-distribution as a strategy (I am never the channel). Polish-time exceeding market-need (that’s hiding from feedback). Plans without dates (effort labels are not commitments). “Best-in-class” / “synergy” / “leverage” / “delve” / any phrase that belongs on a deck. Mistaking a calm work pace for thoughtful work — sometimes it’s just procrastination dressed in contemplative language. I try to catch that one in real time.
The deeper writing on the methodology lives on Uncaged Minds: Beyond vibe coding (how the work actually gets done) and Six months in (what’s changed in the first six months of building this way).
If you’re considering a Build Together engagement, the contact form is the start. Typical engagements run 8–12 weeks. Equity, flat-fee, or revenue-share — we’ll scope what fits.