Every Friday at 4:00 PM, the same dread hit.

My manager's weekly report email would land in my inbox: "Please submit your weekly report by EOD." I'd stare at a blank document, trying to remember what I even did on Monday. Was it Monday I fixed that bug? Or Wednesday?

I'd spend 45 minutes writing something that looked like this:

"This week I worked on the login thing and also had some meetings. Next week I will continue working on stuff."

It was bad. I knew it was bad. My manager probably knew it was bad. But the truth is, nobody likes writing weekly reports. They're a necessary evil—a ritual that eats into your Friday afternoon and makes you question whether anyone actually reads them.

The Breaking Point

The idea for BulletWork came from a particularly painful Friday. I had a week full of work—user interviews, a critical bug fix, a product roadmap review—but when I sat down to write the report, my brain just... refused.

I thought: What if I could just dump my messy thoughts into a box and have AI organize them into something presentable?

Not a generic ChatGPT prompt. Not a template to fill out. Just... type what you did, hit a button, and get a real report back.

That night, I started building.

Week 1: The Ugly MVP

The first version was embarrassingly simple. A single HTML page. A textarea. A "Generate" button. That's it.

Under the hood, it sent your notes to an AI API with a carefully crafted prompt that organized everything into categories: Accomplishments, In Progress, Challenges, and Next Week. The output was clean, professional English—no markdown, no placeholder text, just a report you could copy and paste straight into an email.

I used it myself that Friday. It took me 2 minutes instead of 45. The report actually sounded like a human wrote it—a competent human, even.

I thought: Okay, this might be useful to more than just me.

What Makes BulletWork Different

Yes, you can paste your notes into ChatGPT and ask it to write a report. I tried that. Here's what I got back:

"[Your Name]
[Your Department]
[Date]

Dear [Manager],

I hope this report finds you well..."

Nobody talks like that. Nobody wants to read that.

BulletWork is purpose-built for one thing: turning your scattered weekly thoughts into a clean, scannable report. Here's what that means in practice:

The Solo Founder Reality

I built BulletWork by myself. No co-founder, no team, no funding. Just me, a laptop, and a lot of Friday nights.

Here's what the stack looks like:

It's not fancy. It doesn't need to be. The goal was to build something useful, not something impressive.

The hardest part wasn't the code; it was the prompt engineering. Getting the AI to consistently produce reports that sound natural—not robotic, not overly formal, and not full of corporate jargon—took dozens of iterations. I must have generated 200 test reports before I was happy with the output quality.

Who Is This For?

BulletWork is for anyone who has to write a weekly report and would rather be doing literally anything else. But it's especially useful for:

What's Next

BulletWork is just getting started. Here's what I'm working on:

But here's the thing—I'm building this in public, and I want your input. If you try BulletWork and it doesn't work for you, tell me. If you have a feature idea, tell me. If you just want to say hi, that's cool too.

Email me at hello@bulletwork.so. I read every message.


Ready to reclaim your Friday afternoons?

Turn your messy notes into a professional weekly report in 2 minutes. 3 free reports, no credit card required.

Try BulletWork Free →
Z

Zhen

Solo founder of BulletWork. Built this because I hate writing weekly reports too. Previously worked on product and engineering teams where weekly reports were a way of life.