Engineers don't usually write business proposals. We write code, design systems, maybe push back on requirements. But we don't typically sit down and write a 50-page document outlining product strategy, marketing positioning, and a sales approach. I did, and I'd do it again.
The Context
The company was at a crossroads. Projects were moving slowly, a key deal had fallen through, and morale was low. It felt like we needed quick, impactful wins — not another 6-month roadmap that might not ship.
At the same time, the AI landscape was exploding. Every competitor was shipping AI features. We had built an AI email composer a few years prior, and there had been some bigger AI project attempts since, but they hadn't gained traction. The gap between what we could be doing with AI and what we were doing felt enormous.
Why an Engineer?
Here's what I noticed: the engineers around me had genuinely good ideas. In hallway conversations and 1:1s, people would describe features that could meaningfully change the product. But none of them were raising these ideas formally. The ideas lived and died in Slack threads and coffee chats.
I decided to collect them, flesh them out, and put them into a format that leadership could actually act on.
The Proposal
I spent a Friday afternoon, the entire weekend, and most of my evenings the following week writing a 50-page business proposal. All on my own time — we had pressing projects and I didn't want it to interfere with my work.
The core thesis was simple: rebrand as an AI-driven marketing automation company through a suite of small, composable AI features that build on each other. Not one massive bet, but a series of quick wins that compound.
I outlined three product suites composed of 15 AI-driven projects, along with a strategy for how to position and sell them.
Selling It Internally
Writing the proposal was the easy part. Selling it internally was a crash course in stakeholder management.
I started with my manager, who got excited and escalated it. Our software architect heard about it and did the same. Within days, I had meetings scheduled with engineering leadership and sales leadership.
But it wasn't all smooth. When I brought early ideas to the product team, they pushed back — the ideas weren't concrete enough. Fair. I iterated, made them more specific, and product became more receptive. They told me if I formalized the ideas further, they'd connect me with the relevant product managers.
I learned quickly that different stakeholders need different pitches. I created tailored slide decks for each audience — engineering cared about feasibility, sales cared about positioning, product cared about user value.
What Happened
The core thesis — shifting toward AI-driven products — was adopted as company direction. The sales strategy was implemented. Not everything made it: the full scope was adjusted to match available resources. Instead of three teams working in parallel, it became a focused effort with a dedicated team — myself, a designer, a product manager, a customer success manager, and an ops engineer for consulting.
The first project we shipped? The subject line optimizer I had proposed — a feature that analyzes a user's top and bottom performing subject lines, feeds them into an AI agent to find patterns, and generates optimized alternatives with explanations. It drove a 17% increase in email open rates.
I went from writing the proposal to building the product. That felt right.
What I Learned
The biggest lesson wasn't about business strategy. It was about perspective.
Every engineer I talked to had ideas worth hearing. But they assumed someone else would raise them, or that it wasn't their place. The ideas existed — they just needed someone to collect them, structure them, and present them with enough conviction to get people's attention.
Engineers have a unique vantage point. We see the technical possibilities before anyone else. We understand what's feasible, what's fast to build, and what would actually work at scale. That perspective is incredibly valuable to sales, marketing, and product — but only if we share it.
I'm not saying every engineer should write a 50-page proposal. But I am saying: if you see an opportunity and you care about where your company is going, don't wait for someone else to act on it.