I Built a Social Media Planner That Refuses to Be a SaaS

Most social media scheduling tools seem to assume the same thing:

• you’ll create an account
• connect all your platforms
• store drafts in their cloud
• pay monthly
• eventually automate everything

That works for agencies and larger content teams.

But for me, it always felt like overkill.

So I built something much smaller:

Skedoff — a privacy-first, offline-first social media content planner.

No account.
No cloud sync.
No subscription.
No auto-posting.

Just a simple workflow:

Draft → Queue → Published

You write offline, tag the platform, move it through your own process, and when you’re ready, you manually post on the real platform.

That’s it.

And weirdly, that’s exactly why I think it might matter.

The core idea

I originally thought I was building a lightweight scheduler.

But while building it, I realized I wasn’t actually trying to solve “scheduling.”

I was trying to create a boundary between drafting and impulsive posting.

That changed the product direction a lot.

Instead of building another “all-in-one social media manager,” I leaned into a narrower philosophy:

• planning should be calmer than publishing
• drafts shouldn’t automatically live on someone else’s server
• not every creator needs automation
• sometimes manual control is the feature

So I intentionally didn’t add:

• social account integrations
• auto-posting
• cloud sync
• analytics dashboards
• growth-style productivity bloat

Why I think this is interesting as a product

The product isn’t trying to compete head-on with Buffer/Hootsuite/etc.

It’s positioned more like:

• for solo creators
• for freelancers
• for indie builders
• for small businesses
• for people who want to prepare content without turning it into another SaaS workflow

I think there’s a niche here for tools that are:

• local-first
• privacy-first
• manual by design
• intentionally smaller than the “obvious” category leader

That’s the bet, anyway.

Current status

Right now:

• UI is done
• local DB is done
• core workflow is working
• platform tagging is working
• search/filtering is working
• Android build is prepared

And the app is currently submitted to Google Play for review.

If all goes well, I’m expecting roughly 3–5 days until it goes live (first app review, so I’m trying not to be overconfident 😅).

What I’m trying to protect

The tricky part now is deciding what not to build.

Because the obvious feature roadmap would push this toward:

• account connections
• auto-posting
• backend sync
• more automation
• more “smart” scheduling

And those might make it more marketable in a conventional sense…

…but they also risk turning it into the exact kind of product I was trying to avoid.

So the near-term roadmap I’m thinking about is still aligned with the original philosophy:

• local notification reminders for queued posts
• bulk actions
• better export/backup
• small UX refinements
• maybe optional privacy-respecting crash reporting later

What I’d love feedback on

I’d love thoughts from other founders/builders on this:

If you were positioning this product, would you keep it intentionally narrow — or would you eventually add the “obvious” SaaS features?

Specifically:

1. Is manual posting a valid core feature, or does it limit the product too much?

2. Does offline-first + no accounts + no cloud feel like a meaningful differentiator?

3. Would you position this more for:

   • creators
   • freelancers
   • solopreneurs
   • small businesses
   • privacy-conscious users

Links

• Product page: https://flagodna-developer.github.io/skedoff/
• Original write-up on my blog: https://blog.cahyanudien.site/building-skedoff-i-thought-i-was-making-a-scheduler-but-i-was-really-building-a-boundary

I’m Cahyanudien Aziz Saputra, building under FlagoDNA.

Would love honest feedback — especially from anyone who has deliberately not built the “obvious” version of a product.