SaaS

Our software is used by owners, office managers and bookkeepers at small contractors, and each cares about something different. My homepage tries to speak to everyone and ends up vague. Should I build separate pages per role, pick one audience, or something else entirely?

Our tool is used by teams of 3 to 25 people. Per-seat pricing penalizes growth in the customers we want, but a flat fee means big teams get a bargain. We tried tiers by team size and it confused buyers. What structure kept things simple and fair for you?

We have not changed our $49 monthly plan in three years and costs have risen sharply. About 600 customers pay it, many since the start. I am thinking of moving to $65. Is it better to grandfather everyone, give notice and a deadline, or raise only for new signups?

I am a solo founder with 220 customers and spend about 15 hours weekly answering the same handful of questions. I have a basic help page but nobody reads it. Would in-app tooltips, a knowledge base, or a chatbot cut the volume most? I want to keep a personal feel.

We have $20k MRR growing about 10% a month and a team of five. Advisors suggest anywhere from $500k to $2M. I do not want to give away more than 15% but I also do not want to run out of money in a year. What logic did you use to land on a number?

With a 2-person team and about $6k MRR, our top-requested items are a sync with accounting software and a better reporting page. Customers ask for both roughly equally. Integrations feel like they drive new signups, but reporting seems to reduce churn. How do you decide when you can only ship one this quarter?

It earns around $9k a month with maybe 10 hours a week of work, mostly maintenance. I do not want to sell, yet I feel restless. Should I start a second product, grow this one more aggressively, or hire someone and step back?

Our product helps property managers track maintenance requests. Sales cycles are short but support is done by me alone. A freemium tier worries me because of support load, yet a 14-day trial feels too short for teams that only log requests monthly. Which model has worked for a tool with infrequent usage?

We run a scheduling tool at about $12k MRR with 140 paying accounts. Almost every cancellation happens between day 80 and day 100, and exit surveys just say "not using it enough." We added onboarding emails but the pattern did not change. How do I find out what really happens around that point?