Staging and package edge audit
- What breaks most often: build, test, deploy, release, package publishing, or secrets?
- Which repo is authoritative?
- Who needs to approve releases?
- What does "green" mean today?
- What is the cost of a failed release?
Inquiry
Send a short email.
No form, no autoresponder, no calendar trap. Direct human reply within one business day.
Or copy jess@tinyland.dev and write something brief. Five minutes is enough — I'd rather
get the gist than a polished doc.
If you want to be precise
Use the relevant intake questions below. You don't need to answer all of them — pick the two or three that most accurately describe your situation.
Static spoke launch pass
- What must visitors do: book, inquire, buy, register, read, donate, or attend?
- What content exists already?
- Which brand owns the content?
- Who can approve publication?
- What must be public now vs later?
Scheduling and payment capability audit
- How do clients currently book, pay, reschedule, or follow up?
- Which systems touch the flow: calendar, email, Stripe, PayPal, Venmo, ACH, paper invoices, or booking tools?
- What has to stay manual for now?
- Where do payment or scheduling promises currently get lost?
- What would a safe first integration prove?
What happens next
- I read your email within one business day.
- If the fit is clear, I send a fixed-scope audit proposal.
- For paid work, I send a GnuCash invoice with explicit payment terms before the audit starts.
- If it's not a fit, I'll tell you who might be a better fit.
- Either way, you get a real human reply.
Good first emails
Fastest path
Send the repo, site, calendar, media archive, or workflow that hurts most, plus the deadline you care about.
Best signal
Name the cost of the problem: failed releases, lost bookings, stale content, manual follow-up, or inaccessible media.