3 months ago
Group text message reminders
What is included in the sale ?
This application has been running in production without issue for over 2 years. The website was built mobile-first, is super fast, professionally designed, and has been thoroughly UXed.
I presented on building this app a few times, here are the slides: https://slides.com/tommymarshall/sametimeco
Specifically, you'll be receiving:
- Domain name w/ SSL
- All code, Github-hosted (HTML, SCSS, JS, Laravel/PHP)
- Pusher account for websockets
- Twitter account
- Slack account
- Rollbar.io account
- Google Analytics
What is the technological stack ?
This web app was built for scale in mind by someone who knows what he's doing. Texts are added as jobs and processed off the queue to prevent slow downs, notifications are sent to the client via Pusher, errors are tracked and sent to Rollbar, etc. Social media meta/opengraph were added thoughtfully and integrated (Share on FB to your hearts content). Whether this app has 10 users or 10,000, things will work just fine and the server won't go down.
Which parts of the project are incomplete ?
Nothing. It's complete. You could expand upon an admin panel for direct messaging to/from users.
Do you have any traffic ?
Not much, about 4-10 hits per day. When it first launched on Product Hunt it received a few thousand. Here's the link: https://www.producthunt.com/posts/sametime-co
At it's peak, daily active users were about 60 made up from about 20 groups.
Why are you selling ?
I don't have time to dedicate to it. I have pride in knowing I built this thing and am happy to let someone else take it to the next step.
How can the future owner turn the project into a business ?
Charge per reminder or monthly/yearly subscription for unlimited reminders. Or add some google Adsense to the page, naturally.
Just out of curisoty, how many users do you estimate it'll take before the server expenses increase?
It's not a super straight-forward answer, but this pretty close: To send a text it has to process a job off the queue -- basically every minute it checks to see what Campaigns should be sent out, and throws those texts to send on a queue. The load on the server to do this is super minimal (simple MySQL select + pinging Twilio to send a text). Let's say that every minute of the day it had to send out 200 texts (2 texts per user, since it sends 2 texts per group reminder). This is a reasonable number, though not reasonable in that it would be evenly divided 24 hours a day :) So, sending the same number of texts ever 3 minutes... (24 * 60) minutes a day / every minute * 200 texts = 288,000 texts a day / 2 texts per user = 144,000 active users per day. At that point it's more of a fine-tuning of Twilio's rate limiting (which still wouldn't be hit) and number of workers you want to spin up (which is literally clicking a button on Laravel's Forge). Basically, the server is built to process jobs as it seems fit. A beefier server could handle more jobs at a time, but like I said, the work is minimal. Hope that helps! :)