If you’re a small business owner or someone who’s just dipping your toes into the world of “By Application” services, let me start with a little context: I run a small, tight-knit operation that builds custom tools for other small teams. When people ask me how “By Application” works for a business like mine, I get it—this model isn’t as flashy as off-the-shelf software, and there’s way less info out there about how it actually works for someone who’s not a huge corporation. No hype, no jargon, just the real stuff from someone who’s lived it for the past six years. By Application
First off, let’s cut through the confusion: “By Application” isn’t some weird, untested loophole. For our business, it’s a way to skip the one-size-fits-all junk that most big tech companies push. Instead of selling a generic product to anyone who’ll click “buy,” we build something specifically for a single client’s unique needs. Yeah, that means no volume discounts, no pre-made templates you have to force your workflow into, and way more back-and-forth than you’d get from a company with 10,000 employees. But here’s the thing: for small teams that don’t have the time or budget to hack together a tool on their own, that back-and-forth is exactly what matters.
Let’s break down how this actually plays out step by step, from the first time a client slides into our DMs (or sends an email, because not everyone uses DMs for business) to the final launch. When someone reaches out, they almost always start with a problem. It’s never “we need a new tool”—it’s “we spend 10 hours a week manually reconciling invoices from 5 different vendors” or “our part-time field techs can’t log their work orders without using a clunky app that breaks when they get bad cell service.” Those are the kinds of pain points we live for. I don’t have a sales team to pitch fancy features no one asked for; my job is to listen. Last month, a café owner told me their current POS made it impossible to track which pastries were selling best for custom orders. That specific, tiny problem? That’s the start of a By Application project.
Next comes the “application” part—wait, not the client filling out a 10-page form (thank god). For us, the “application” is a 30-minute call. I don’t send a generic form with 50 questions because half the time, those are just hoops. Instead, I ask two core things: “What’s the exact thing you’re wasting time on right now?” and “If you had a magic fix, what would it do that your current setup won’t?” Sometimes, clients will ramble about other things they want, but we reign it in—this isn’t about building a Swiss Army knife. It’s about solving that one specific pain point first. Last year, a landscaping company wanted to track equipment maintenance, but they also asked for a payroll tool, a client contact manager, and a route planner. We told them to focus on maintenance for the first version—add the other stuff later when they’re not juggling 10 new features at once. That’s a key part of how we make it work for small businesses: no scope creep, no overpromising.
Once we nail down the exact problem, we draft a super simple proposal. No 20-page legal document, just a 1-page outline that says: what we’ll build, how long it’ll take (usually 2-4 weeks, depending on the complexity), what the rough cost is, and what’s out of scope. For a small café, that might be a $1,200 one-time fee for the pastry tracking tool, plus $50 a month for hosting and support. For a landscaping company, it was $2,800 to build the maintenance log, plus $75 a month. We’re not out to make a killing—we price it so small teams can afford it without going into debt, because if they can’t pay, we don’t get a long-term partner. A lot of people ask why we don’t charge a subscription only, but here’s the thing: small teams hate recurring fees. If we give them a one-time purchase option with a small monthly support fee, that’s way easier for someone who’s just scraping by.
Then comes the build phase—and this is where “By Application” is nothing like a regular software project. We don’t build something in a vacuum and then drop it on the client’s lap. Twice a week, we send a quick update: a screenshot of what we’ve built, a 2-minute Loom video showing how it works, and a list of questions. Last quarter, when we built a work order tool for a HVAC company, we sent a screenshot that had a typo in the tech’s name field. The client pointed it out, and we fixed it in 10 minutes. A big company would’ve charged for that, but for us, it’s part of the process. We also schedule a 15-minute mid-project check-in to make sure we’re not missing something. Once, a dog daycare client told us they forgot to mention they need to track vaccine expirations for their pups—we added that in, no extra cost, because it was a tiny change that made the tool actually useful for their day-to-day.
The launch? It’s not a big party. We send a walkthrough video, set up a 30-minute call to answer questions, and then we’re on call for the first week. If the café owner can’t figure out how to pull a pastry sales report at 8 a.m. on a Saturday, I’m there to walk them through it. That’s another big difference from off-the-shelf tools—most of them have a help center with 100 articles, but no one to actually talk to when you’re panicking because you need to close out the day. Our support isn’t a call center in another country; it’s me, and sometimes my part-time helper, who used to run a small retail shop so she gets the chaos of small business life.
Wait, let’s be real here—this model has downsides. Last year, a client asked us to add a feature that we knew would make the tool too clunky, and they were upset when we said no. Another time, a landscaping company’s business changed, and their tool for tracking mower maintenance ended up being useless, so they didn’t renew their support plan. But those are small, growing pains. For every client that leaves, we have two more that come back and say, “This tool cut our admin time in half.” That’s the win that keeps us going.
A lot of people compare “By Application” to custom websites, and yeah, there’s overlap, but it’s not the same. Custom websites are usually just a static page, but By Application tools are interactive, integrated with whatever the client already uses—like their Google Calendar, QuickBooks, or text message service. For the HVAC company, we integrated their work order tool with their existing Google Calendar so techs can see their appointments without logging into a separate app. For the café, it integrates with their Square POS so they don’t have to manually enter pastry sales. That integration is the part that makes it way better than just a custom spreadsheet, which most small teams use right now.
Another thing people don’t talk about: how this model forces you to stay small. We could easily take on bigger projects, but we choose not to because if we do, we’d lose the personal touch. When a client texts me at 9 p.m. on a Tuesday to say their tool isn’t working, I don’t have to forward their message to a support team. I can fix it in 15 minutes. That’s a perk of being a small business that uses the By Application model—we’re not a cog in a machine. We’re the people who built the thing, so we know every line of code, every quirk, and exactly how to fix it.
If you’re thinking, “Hey, this sounds like something I might need,” let me tell you who this is for. If you’re a small team (1-20 people) that’s sick of wasting time on admin, can’t find an off-the-shelf tool that does exactly what you need, and don’t have the budget to hire a full-time developer, this is for you. It’s not for a huge corporation that needs a tool for 500 employees—for that, they’d go with a big tech company. But if you’re a café, a landscaping crew, a dog daycare, or a small trade company, this model works. It’s not fast, it’s not cheap (in the sense that you’re not paying $10 a month), but it’s worth it because it’s built for your specific problems, not someone else’s.
I’ll wrap this up with a quick note: at the end of the day, “By Application” for a small company isn’t about being fancy. It’s about solving problems for other small people, by listening, building slow, and not overcomplicating things. If you’ve got a pain point that’s driving you crazy, feel free to reach out and let’s chat. No sales pitches, no hidden fees, just a conversation about what would make your life a little easier.
Sportswear Fabric References:
- Small Business Administration. (2022). Custom Software Solutions for Small Enterprises. U.S. Small Business Administration.
- Harvard Business Review. (2021). The Value of B2B Custom, Application-Based Services for Small Firms. Harvard Business Publishing.
- TechRepublic. (2023). Avoiding Off-the-Shelf Software Pitfalls for Small Teams. TechTarget.
Hangzhou Kangsheng Textile Co., Ltd.
Address: 22# Building, K7 Original park,No.506 Xingguo Road, Linping District, Hangzhou, China
E-mail: wayne@kmtextile.net
WebSite: https://www.kangshengtextile.com/
