Why I'm writing a blog about scheduling

Scheduling is one of those subjects nobody thinks deserves an essay. It sits in the same category as filing taxes or sorting the recycling — necessary, recurring, slightly tedious, and beneath the dignity of anyone's serious attention. We've collectively decided it's a solved problem. The solution is a booking link. Move on.

I think the consensus is wrong, and I think it's wrong in interesting ways. So I'm writing about it.

This blog is the long-form version of the work I'm doing on Proffer — a scheduling tool I built for the kind of professional meetings the existing tools were never designed for. The product is the practical answer to the question. The blog is the place where I get to think out loud about why the question was worth asking in the first place.

A few things you can expect from what shows up here.

It will be specific. Most writing about scheduling — to the extent any exists — is generic productivity advice. Block your calendar, time-batch your meetings, decline the ones you don't need. I'm not going to write any of that. The interesting questions aren't about productivity; they're about the social transactions hidden inside scheduling, and about the particular professional contexts where those transactions matter most. Federal judges. Senior partners. Executive coaches. Long-standing client relationships. The places where the way you ask for a meeting carries weight independent of the meeting itself.

It will have a point of view. I've been building software for thirty years, and one of the things I've learned is that every tool encodes a worldview, whether the people who built it intended one or not. Calendly encodes one worldview about scheduling — a brilliant one, well-suited to the markets it dominates. Proffer encodes a different one. Saying so out loud is more honest than pretending I'm building something "neutral" or "objective." There's no such thing.

It will admit when the other side is right. Calendly is a great product for a real job. So is Doodle. So is whatever scheduling assistant your CRM ships with. None of them are wrong; they're just optimized for situations that aren't the same as the situations Proffer is optimized for. A lot of what I want to write about is how to tell which situation you're in. That's not a competitor takedown; it's a guide for the reader to figure out what they actually need.

It will be short. I've read too many founder blogs that turn every observation into a 4,000-word essay because the founder mistakes length for seriousness. The opposite is closer to the truth. A clear thought in 700 words is harder to write than a fuzzy one in 2,500. I'm going to aim for clear.

It will not be a content marketing operation. There won't be SEO-bait listicles or "10 ways to optimize your meeting schedule" headlines. The reason for that is partly aesthetic — I don't enjoy writing them and you don't enjoy reading them — but mostly strategic. The people I'm building Proffer for don't respond to that genre of writing. They respond to the same things they respond to in their professional reading: real thinking, plainly expressed, by someone who has spent enough time inside the problem to have something specific to say. So that's the kind of writing this will be.

It will publish on Tuesdays. Roughly once a week, with the discipline to skip a week when I don't have anything worth saying. A skipped week is invisible. A weak post is loud.

I'm starting this blog because Proffer is a small idea about a small subject, and I've come to think small ideas about small subjects are where most of the interesting writing actually lives. The big-idea pieces have been written. The category-defining essays already exist. What's underwritten is the close attention to the small ways software shapes the texture of professional life — the choices that look minor until you notice you've been working around them for years.

Scheduling is one of those textures. It's worth a few essays. Let's see where they go.