Building four products at once: how the portfolio model actually works
The Keyser Forge model: one consistent operating system across several products, the daily marketing flywheel, and the honest tradeoff of the support tail.
Short essays on the social side of scheduling, the design choices behind Proffer, and the lessons that keep showing up as I build.
The Keyser Forge model: one consistent operating system across several products, the daily marketing flywheel, and the honest tradeoff of the support tail.
A walk-through of Group Proffer's logic: why the sender picking candidate times beats letting everyone propose, and the spreadsheet meeting nobody named.
Microsoft Graph Mail.Send as a design choice, and what sending from your actual mailbox preserves: deliverability, sender identity, the relationship.
YAGNI in practice, told as a story: the temptation to over-architect for an imagined future, and the cost of building for a future you haven't earned.
A build-in-public case for narrow scope: why launching focused on Microsoft 365 beats launching half-built for everyone.
What the three-times pattern accomplishes socially that a booking link doesn't: specificity as respect, constraint as a gift to the recipient.
Hospitality used to be the default in professional scheduling. Software talked us out of it — and we forgot we ever had the choice.
On the grassroots experiment of replying to scheduling links with a different kind of scheduling — and what it taught me about the product I'm building.
Booking links work great for some scheduling. They go strange for the kind that's built on respect. A short reflection on why.
Scheduling is one of those subjects nobody thinks deserves an essay. That's part of why I'm writing one.
Connect Outlook, pick a few times from your real calendar, and send one to your own inbox to see exactly what your recipients see. Five Proffers a month on the free tier. No card required.