Import the repository
Use GitHub context instead of rebuilding a product brief in another tool.
'/%3e%3cpath%20d='m21%2023.3%2010-5.7%208%204.5-10%205.8%2014.2%207.9v6.6L31%2049.5l-8-4.6%2010.1-5.8L19%2031.2v-6.7l2-1.2Z'%20fill='%23fff'/%3e%3c/svg%3e)
Social media for indie hackers
Ship the product and the story without pretending you have a content team.
Convert the work already captured in your repository into a small, credible publishing plan instead of opening a blank composer after every release.
For solo founders and tiny product teams balancing development, support, sales, and marketing.
founder/tinyinvoice
Latest releasev0.9 — Recurring invoice reminders
Repository context becomes an editable campaign—not an automatic publish.
The problem
The blank page arrives precisely when your energy is gone.
Launch-day writing competes with deployment checks, support, documentation, and the next bug report.
Posting only product announcements makes an account repetitive and gives readers little reason to respond.
Broad marketing suites demand more setup than a small team can justify.
The workflow
Start with what you shipped, then broaden the story.
Correct the audience
Add the customer perspective that source code and release notes cannot know.
Generate a compact calendar
Choose three posts for a quick release or twelve posts for a month-long sequence.
Edit in one sitting
Review all drafts together, adjust dates, and return to building.
Example output
One release. Three useful angles.
founder/tinyinvoice · v0.9 — Recurring invoice reminders
01Customer problem
Late invoices often start with a reminder no one had time to send. TinyInvoice v0.9 adds recurring reminder schedules for solo businesses.
02Build in public
I expected recurring reminders to be a scheduling problem. The real edge case was preserving the customer’s timezone after daylight-saving changes.
03Question
Solo consultants: do you want invoice reminders to sound consistent, or should each reminder become progressively more direct?
What changes
Less blank-page work. More deliberate communication.
- Less launch-day writing
- A healthier mix of post angles
- A schedule that survives busy weeks
- A path from free generation to publishing
Questions
Practical details.
Is the free plan enough for one product?
It supports one project, one campaign, three networks, and three plan generations per month—enough to validate the workflow.
Do I need to connect every social account?
No. Create and review the calendar first. Manual and assisted publishing remain available when direct connections are not configured.
Can I change the tone?
Yes. The wizard provides an editable tone field before calendar generation.
Use the repository you already have
Generate the first three posts now.
No signup for public repositories. Preserve the result when you are ready to build the full calendar.