Real lessons, monetization strategies, and new methods from people building and growing a one-person web or app business.
GRIT started as a fitness app meant to bring workouts, food tracking, progress tracking, and an AI coach into one place. The fitness app market was already crowded with calorie trackers, workout planners, AI coaches, and progress tools, but existing options felt expensive, split across too many apps, or not built in the right way. The first version included weight tracking, workout planning, calorie tracking, and AI-made workout and meal plans. The features worked, but the app was not something its maker would have wanted to download. The design was weak, and the AI coach felt more like ChatGPT with a fitness prompt than a guide that adjusted to a person’s real journey. The biggest problem was that GRIT did not give people a clear reason to choose it over hundreds of other fitness apps. The main lesson is that building working features is different from building a product people understand, want, and choose.
A solo (or small-team) developer built a two-sided vehicle safety checklist app for the road transport industry, relying heavily on AI pair-programming (Claude) during development. Drivers fill out pre-trip and in-trip inspection checklists from their phone, and the app works offline, queuing entries locally and syncing automatically once back online. The transport company watches everything live from a web dashboard, including in-progress trips and completed inspections, and can generate PDF certificates for compliance and audit purposes. The stack is a React 19 single-page app with TypeScript in strict mode, backed by a serverless Postgres backend-as-a-service that provides authentication, row-level-security-enforced multi-tenancy, realtime subscriptions, object storage, and edge functions. PDF certificates are generated client-side. The app has so far only been validated with a modest user base, but a new contract with a large client is about to onboard roughly 1,000 drivers almost overnight, prompting the developer to ask what to stress-test before go-live.
Use Google PageSpeed Insights on the screens customers actually use, such as the dashboard and checkout, rather than checking only the marketing page. In repeated firsthand checks, many no-code apps scored between 30 and 50, with some in the 20s. A rough industry estimate suggests that each extra second of loading can reduce conversion by about 7%. On that basis, an app that takes five seconds to load can produce meaningfully fewer signups or purchases than one that loads in 1.4 seconds, even with the same traffic and product. Customers rarely report that an app felt slow; they simply leave, so the operator may mistakenly blame the wording or price. Measure the main product screens before spending more money or effort on attracting visitors.
In one firsthand solo software business experience, the monthly price stayed at $5 for too long because charging more felt likely to stop people from buying. The low fee instead attracted customers who canceled over small bugs, created heavy support demands, and expected service far beyond what they paid. Raising the price to $19 did not make new sign-ups disappear. It reduced interest from casual shoppers while bringing in more customers who had a real problem to solve. Those customers stayed longer and complained less because the service was worth paying for in their situation. The original low price reflected the owner's fear that the product lacked value, rather than clear evidence that the market would reject a higher price.
After Mycro, a weight loss app, reached production, the hard part turned out to be getting people to care and sign up, not building the app itself. Product work felt familiar and comfortable, while marketing, distribution, and being visible felt much harder. The better path would have been to write about the weight loss problem earlier, talk with people trying to lose weight, test messages, and learn what made someone willing to sign up for updates. Building for months first and only then asking how to get users creates a painful gap. Audience building should happen while the product is being built. Younger builders and first-time founders should not wait for v1.0 before they start finding interested people.
Running a small AI tool in the cloud means every free user creates an ongoing inference cost. The free plan may attract potential customers, but the operator keeps paying when those people never upgrade. To avoid that burden, the product was changed so the AI work runs directly on each user's computer. This makes free users cost almost nothing to support, but removes sync between devices and access from a phone. Those limits initially seemed likely to make the product less convenient than its rivals. They also created its clearest difference: the tool works locally and users keep control of their own data. Adding cloud features again could weaken both the low-cost model and that reason to choose the product.
When it is unclear who will buy a product, start by examining a similar business. The central claim is that a comparable product or service already exists roughly 999 times out of 1,000. Study what it offers, who uses it, and how your product would be similar or different. Existing customers may like one feature but dislike another, or they may object to the price, brand, or owner. Those dislikes can reveal an opening for a new product, with an audience that already exists rather than one that must be created from scratch.
This AI tool can take one photo of an object, such as a toaster, and turn it into an editable CAD model. The generated model includes named parts and working joints. A change request can be attached to one part, such as asking for the top edges to be beveled, and the tool edits only that part. It then checks the shape again before returning the updated model. The result can be exported as a STEP file instead of a simple mesh. That means it can open in Fusion 360 with a feature tree, so an engineer can continue the work in a normal design workflow. The tool is still early and free to try.
A developer who burned out after six months of building an app took community advice and added a paid subscription tier. The core features that make the app useful stayed completely free, while only extras were locked behind the subscription; some minor features were even removed to keep things clean. The rollout was gradual, with no dark patterns or nagging prompts. Out of roughly 2,500-3,000 monthly active users and 7,800 total registered users, only 18 people subscribed. The developer doesn't think the app itself is bad, but sees the outcome as a clear failure.
The First Look is a database and map with real price information for more than 4,000 wedding venues in the United States. Wedding venues often hide prices until a couple fills out a form, takes a sales call, or visits in person. The service collects quotes from couples who recently searched for venues and pricing PDFs sent by the venues themselves. Those submissions are parsed and added so the next couple can compare prices faster. After more than three months of work, a stranger paid $19 for access. A new subscription tier for wedding planners is now live, which tests whether business users will also pay. The story also carries a push for women with unfinished side projects to keep shipping and reach a first sale.
Keepyy is a personal app for small everyday problems like forgetting where a passport is stored, who borrowed a charger, or whether an item was returned. Existing tools were mostly built for business inventory, not for simple personal use. Keepyy lets people record lent and borrowed items, save where important belongings are kept, and search those records quickly. It is aimed at students, families, professionals, and anyone who sometimes forgets where their things are. The app is still being improved, and user feedback is being used to shape what comes next.
A 60-second demo that rushes through sign-up, the main screen, settings, connections to other tools, and pricing can feel crowded and be hard to remember. A clearer demo focuses on one concern a potential customer has. That concern might be whether setup is difficult, whether the product can handle messy data, why it is better than a spreadsheet, or what happens after an account is connected. Show the situation before the problem is solved, then the exact moment the product removes that problem, and stop there. Five concerns can become five short clips instead of one long tour that viewers may not finish. Each clip can sit beside the matching section of a product page, where that concern is most likely to arise.
Drawing on a track record of launching 8 products in 18 months and generating 2-3 million organic Reddit views with zero ad spend, turning into thousands of users, the advice is that most founders fail not because they're bad at marketing but because they post in the wrong places. Posting in r/startups or r/SaaS mainly reaches other founders, not real customers. Actual customers gather in niche subreddits complaining about the exact problem a product solves, often communities founders have never heard of because people are there for reasons unrelated to the product. Finding these subreddits requires thinking through who the customer really is, what else they care about, and where they hang out, then digging through Reddit to find the active ones. This is described as high-leverage but tedious work that almost nobody does. To remove that tedium, a tool called sentrive was built to automate finding relevant niche subreddits, and readers are invited to share their product for suggestions.
AI now makes it easier to build a small web or app product over a weekend and show it to people quickly. If people show interest, business formation, a bank account, payments, invoices, and expense tracking can become immediate problems instead of later tasks. It used to feel reasonable to handle business setup only after a project clearly worked. That timing may be too slow when someone is ready to pay soon after seeing the product. Not every weekend idea needs a company behind it. But if serious effort goes into a product, the basic business setup may need to be considered before the first paying customer appears.
SocialKit, a social media scraping API, reached roughly $3,300 in monthly revenue about a year after launch ($2,500 from subscriptions plus $700-1,000 from one-time purchases). It has over 18,500 users, with more than 140 paying customers. Growth was gradual: $13 in month 1, $118 in month 3, $370 in month 5, climbing to the current $2,500 recurring level. The main growth driver was SEO started from day one, including blog posts, free tools, competitor comparison pages, and YouTube videos, which brought in most customers organically. Talking directly with users, including over WhatsApp, and staying consistent also contributed to growth. Looking ahead, new APIs are being built for AI agents, using MCP (a protocol that lets AI agents talk to outside tools) and agent skills, so agents can pull transcripts, comments, and stats directly from social videos.
Four years of building iOS apps led to 7 apps, about 2,600 total downloads, and €51 in revenue. The builder first learned to code because making apps that other people could install felt meaningful, even though the main job is now in data and artificial intelligence. The long-term goal was to create things people use and eventually earn some money from them. Most apps started from personal problems, and monetization was mostly ignored for years. The current target is €100 in monthly recurring revenue. The listed apps include Chronicles, a newly released artificial intelligence voice journal; Busfahrer, a German drinking card game with 578 downloads, a 4.7 rating, and €39 revenue; Doomsday Method, a tool for learning Conway's method to find the weekday of any date, with 733 downloads and no revenue; WorkoutPulse, a HIIT and Tabata timer with 761 downloads, a 4.9 rating, and no revenue; Tick, a simple habit and task tracker with 247 downloads, a 5.0 rating, and €9 revenue; and Leben in Deutschland Pro, a German citizenship test preparation app with 68 downloads, a 5.0 rating, and €3 revenue.
StepNest is a step tracker now live on Google Play. It has no ads, and it does not require an account or login. Step data stays on the phone. The app counts steps using only the phone’s built-in sensor, not GPS, so it should use less battery. It shows two streaks: one for keeping the habit going and one for hitting a goal. Each month, a person’s steps add to their country’s total, and countries compete on a worldwide leaderboard. The paid model is a one-time lifetime unlock instead of a subscription. The app does not keep a background service running; it rebuilds the day’s steps from sensor snapshots when the app is opened, keeping battery use low.
Produchive is a desktop app that records computer activity and helps judge whether time is being used productively. It works on Windows and Mac and was built with Electron. User data stays on the person’s own PC in a JSON file instead of being sent to an outside server. The app is designed to work fully offline. It can use downloaded open-source LLM models through WebGPU to judge productivity. The project started from a personal need to reduce procrastination on a PC and took about five months to build. It has not been published in any app store yet, but it is described as fairly stable.
A three-year developer training program found that the biggest blocker was not basic coding skill but knowing what to build. The program worked with hundreds of people, including computer science students, new graduates, and experienced coaches, yet many arrived with no clear direction on day one. Their resumes and GitHub profiles often contained the same kinds of AI-made sample projects, clone apps, landing pages, and tutorial code. When tutorials were removed and they had to build something useful for a specific real job, many got stuck. They had little access to real guidance, little sense of whether their code mattered to a company, and few ways to prove they could work on real company systems. Even coaches often worked without enough contact with real workplace needs because the gap between school and work was so large. The modern path into tech can leave developers isolated, guessing what companies want, writing code nobody reviews, and hoping an automatic resume filter notices them. Manual mentoring helped with this problem, but it was hard to grow at scale.
Forget My Car is an iOS app for finding a parked car in large underground garages. GPS can fail underground, show the wrong floor, or only place the car somewhere inside a building. The app works by tapping "I Parked," taking a photo of the parking spot, and typing a floor or nearby marker such as "B2, near the blue pillar." The saved note stays on the Lock Screen, so the driver can check it without unlocking the phone. A paid-parking timer warns the driver 10 minutes before time runs out. There are no accounts, no cloud storage, and no ads. Photos and parking details stay on the device. The app avoids a backend because the job is simple and the parking photos do not need to sit on a server. It costs $1.99 as a one-time purchase, is live on the App Store, and was built solo with Expo and React Native.
A cat died after eating part of a lily. Lilies can be deadly to cats, and even pollen or water from the vase can damage their kidneys. Less than 30 minutes passed between seeing the cat nibble the plant and getting her admitted to the hospital. The vet’s instructions were followed, but the cat still did not survive. For six years, the home had no flowers or plants except cat grass and rosemary, yet one gifted lily was not recognized as a danger in the moment. One missed risk was enough to cause a permanent loss. A first project that was expected to be fun has become a project meant to help other people avoid the same kind of loss.
A free scanner checks whether a local business appears in AI recommendations. After entering a business name, city, and category, it asks ChatGPT, Perplexity, and Gemini the kinds of local questions a real customer might ask, such as looking for the best dentist in a city. The result shows whether each AI tool recommends the business, which competitors are named instead, and where the business appears in the list if it is included. In a test of 50 local businesses, most did not appear in any AI answer. The businesses that did appear were not simply the ones with the highest Google ratings. The early signal is that AI answers may care more about mentions on local websites and consistent information across the web than raw review counts. Seeing a screenshot of ChatGPT recommending a competitor made the issue feel concrete for business owners, and some reacted strongly. The scan is free and shows the result before signup.
OpenWhen has a web page where people write a letter to their future self and keep it closed until a chosen day. The idea comes from a common problem with future-email services: a personal letter can later arrive in the same inbox as bills and newsletters, which can make the moment feel ordinary. One large similar service now limits free letters and shows ads around them. OpenWhen lets someone write one honest page and lock it until a date, or behind a question only their future self could answer. When the time comes, the reader presses and holds a wax seal on the screen until it breaks and the letter opens. It works without an app, without an account, and for free.
When building a side project, comparing only similar apps can point attention at the wrong target. A small Mac tool for screen recording or presenting is the example. It helps direct attention on screen with live zoom and highlighting. The real alternatives people already use are not usually paid competitor apps. They are free workarounds such as shaking the mouse so the cursor becomes easier to see, using Zoom annotation arrows, or verbally guiding people to the right part of the screen. In that situation, more features do not automatically win. The product has to be clearly better than the free workaround, enough to overcome switching friction. The likely customer is not always shopping for software; they may simply be someone who has learned to tolerate a small repeated annoyance.
Firsthand experience shows that AI agents used for coding can lose direction after a short work session. More time can go into reminding the tool what is being built than into writing the product itself. The main problems are hallucination, where the tool makes things up, and infinite loops, where it keeps repeating unhelpful work. A set of agent instructions was created to give the AI clearer rules to follow during coding. The rules may be more detailed than necessary, but they helped reduce frustration during real work. The instructions were open-sourced in a GitHub repository, with an invitation for others to suggest better ways to make AI coding tools less unreliable.
A Google Sheet can be used as the source for website data and AI tools. The problem started with a public FAQ kept in Google Sheets, where another sheet-to-API service had such a small free limit that the page became empty when the limit was reached, without a clear warning. The new service lets someone paste a Google Sheet link set to “anyone with the link” and receive a hosted, cached JSON endpoint in about a minute. The same pasted link also creates an MCP server, so tools like Claude or Cursor can read the sheet directly. It does not require a Google Cloud project, an OAuth screen, or a service account file. A search widget can be added to a webpage with one script tag. The service is read-only, so an AI tool cannot overwrite the sheet, but people who want write access may see that as a limit. Some error messages still need improvement.
Fixel AI is a free AI tool for home repair questions. A person can describe a broken item or upload a photo, and the tool sorts the job into three levels: safe to fix yourself, possible but needs care, or better handled by a professional. It is meant for everyday problems such as a leaking tap, a running toilet, or a light switch that sparks. When the job looks safe, it gives step-by-step repair guidance. When the job involves risky areas such as electricity, gas, or structural work, it does not give repair instructions and instead writes a short message that can be sent to a repair worker. The tool changes its suggestions by country: Bunnings and hipages in Australia, Home Depot and Thumbtack in the United States, Screwfix in the United Kingdom, and Tokopedia and Shopee in Indonesia. It also shows prices in the user’s local currency. It is free, needs no signup, and works in desktop and mobile browsers.
Startup research can begin by looking for the boring tasks people hate doing again and again. The useful questions are what work they do, which task they dislike most, how often they do it, and why it is still manual. It also matters whether they tried software before and why it did not solve the problem. Another key question is how much better their day would be if that task disappeared tomorrow. The main idea is to look for specific, repeated frustration instead of exciting-sounding ideas.
Selling SaaS to large companies often requires more than a product pitch. During the buying process, an enterprise security questionnaire can force the team to gather security policies and confirm technical details. Old documents may need to be found, and engineers may have to join the sales process to answer accurately. Many early-stage SaaS teams are not fully ready for this the first time. The practical issue is what part of this process catches teams off guard and how they get through it.
Many SaaS products are built around separate pages instead of the way work actually happens. A user may need one page for customer information, another page to dispatch a technician, another page to create an invoice, and another page to check inventory. The software still works, but the user has to stop, move somewhere else, finish a small task, and then remember what they were doing before. When this happens hundreds of times a day, the mental switching becomes part of the job. This page-and-menu model may mainly exist because web business apps have copied the same design pattern for about 20 years. A better direction is to let needed actions appear inside the current workflow instead of turning every task into a separate destination.