ProstePosty: a portal that posts ads to Facebook groups
The owner of a mini-excavator or a car-buying business belongs to dozens of local groups and loses hours every week pasting the same ad into each one. This is a finished product with an account, a plan and a container of its own that does it for them, slower than they would like, and that is a feature.
Industry: Small service and trade businesses, SaaS product
In short
- 5,344 posts published by the product's engine in three months
- 609,646 impressions on those posts over 90 days, per Facebook's own stats
- 71 days of uninterrupted operation on one account without a block
- Two plans: 199 and 499 zloty a month, seven-day trial with no card
About the project
The customer is a small service business owner: car buying, mini-excavator work, a sawmill, renovations, beauty. They have an offer, a Facebook account, membership in dozens of local groups, and every week they paste the same ad into each one by hand. This is not a tool for agencies; it is a product for a one-person company.
The challenge
An automation that posts to Facebook has two ways to hurt its customer: get their account blocked, or promise results it cannot deliver. What was needed was something that moves slowly, states plainly how many posts will not survive moderation, and stops itself the moment Facebook starts asking questions.
Goals
- Take hours of manual posting off a small business
- Avoid getting the customer's account blocked
- Show proof that a post actually landed, not just a counter
- Sell self-service, with no sales call before the start
Technical challenges
The Facebook password never touches our server
The customer signs in themselves, in a real Chrome window running inside their own container, which they see in their browser. Once the login is detected the window closes and the browser profile stays in the container. We never see the password and never store it.
One container per customer, not one big application
Every customer gets their own container, volume, database, browser fingerprint and dedicated static IP. Facebook does not tie the accounts to one device, and a failure or a block hits one customer rather than all of them.
Slow pacing as a feature, not a limitation
Posts go out at random intervals, within an hourly window, under a daily cap derived from the group pool, and the copy rotates between variants. That comes from safety limits that cannot be overridden.
Proof instead of a counter
After publishing, the system checks whether the post survived and shows a link and a screenshot. When Facebook asks for verification the automation stops itself and tells the customer what to do.
Solution and implementation
A portal a business buys and starts on its own
You create an account, sign in with an SMS code, connect Facebook, pick your groups and describe your offer in one paragraph. For seven days the ads go out for real, and you are invoiced only if you decide to stay.
prosteposty.pl: a sales page with a preview of the customer panel, production numbers and two plans.
A section about what the product does not promise
Stated openly on the page: roughly a third of posts wait for a group admin's approval, between twenty and forty-seven percent disappear to moderation, and nobody rules out an account block. The figures come from 5,344 posts by the same engine.
Two databases that deliberately cannot see each other
The shared database holds metadata only: who the customer is, what they bought, whether their container is alive. Campaign content and the Facebook session live in the database inside the customer's container, invisible from outside.
Results
A proven engine, not a prototype
The publishing code was not written for this product. It is a tool ported to Linux that has run 5,344 posts in production, complete with block detection and post verification.
The customer pays only after checking
Seven days run for real, on the customer's groups and from their account. No card, no contract, no upfront fee.
Hours a week taken off the owner
Handling forty groups, which used to take several hours a week, comes down to a few minutes of reviewing results.
Takeaways
Honesty about limits sells better than a promise
Stating outright how many posts disappear to moderation filters out customers who would have left after a month with complaints anyway.
Isolation is a requirement, not a luxury
When you automate someone else's accounts, a separate container, browser fingerprint and IP address decide whether one customer's block drags the rest down with it.
Scope
- SaaS product from scratch
- Customer panel and billing
- Container isolation
- Publishing engine
Technologies
- Next.js
- Express
- PostgreSQL
- SQLite
- Docker
- Traefik
Frequently asked questions
How is this different from the desktop tool in the other case study?
That one is a tool for a single company, run on a computer, where a person approves every post. ProstePosty is a finished product: you create an account, buy a plan, get your own container, and publishing runs on its own.
Does my Facebook password reach your server?
No. You sign in yourself in a Chrome window running inside your own container. We never see the password and never store it.
Could my account get blocked?
It is possible and nobody rules it out. That is why the pacing is slow, the limits are hard-coded, and the system stops itself at the first sign of a verification request.
How many posts actually show up?
Around a third wait for a group admin's approval, and between twenty and forty-seven percent disappear to moderation. You can see which ones, so you can pick better groups.
What does it cost?
The Local plan is 199 zloty a month, the Business plan 499 zloty a month, excluding VAT. The first seven days are free and the invoice comes only once you decide to stay.