--- title: What Tech Does My One-Person Business Need? url: https://varstatt.com/jurij/p/what-tech-does-my-one-person-business-need author: Jurij Tokarski date: 2026-10-19 updated: 2026-10-26 description: A new coach has a site builder, booking tool, Stripe and newsletter that don't talk. One tool per job, connected so a client is entered once, in your name. section: Blog (https://varstatt.com/jurij/archive) tags: Q&A (https://varstatt.com/jurij/c/questions) --- I'm going solo as a coach. I've signed up for a website builder, a booking tool, Stripe and a newsletter, and none of them talk to each other. What do I actually need, and how should it fit together? One tool per job: a domain with email, a site, booking, payments, a client list and one place for automations. Connected so a client is entered once, and all in your own name. The four tools in the question cover the site, booking, payments and the newsletter. What's missing is the client list and the place for automations. Without those, nothing carries a booking from one tool to the next, so the coach does it by hand. So connect before adding, and keep each tool only while it earns its place. ## One Tool per Job A one-person business runs six jobs online, one tool each: 1. Domain and email: your name on your own domain, and an inbox that uses it. 2. Site: where people find what you sell and book the call. 3. Booking: a booking page that takes payment. 4. Payments: payment links or a checkout, in your own account. 5. Client list: one place for every client, instead of three. 6. Automations: one place for the flows between the other five. Beside them sits a password manager, with every login in your name. Fewer tools are better here. Each one adds a login, a renewal and one more thing to break. That's why I [consolidate](/principles/philosophy/consolidation) before I add. Six tools still don't make a setup. What makes one is how they connect. ## Enter Each Client Once A booking should reach the calendar and the client list on its own. A newsletter signup should land in the same list. Without that, you are the connection: each booking copied by hand into the calendar and the client list. The flows need one home. Zapier, Make and n8n all do the job. Three questions pick between them: who pays per run, who edits the flow later, and where it runs. [Should I Use n8n, Make or Zapier?](/jurij/p/should-i-use-n8n-make-or-zapier) walks through that call. Flows already running somewhere can stay there. Keep what works, and move a flow only when its bill outgrows the job. The site is the one tool in the list with two bills. ## The Website Is Two Bills The first bill is the build, and it should buy more than a design. Most small business sites stop at the design and go quiet after launch. What keeps one working is the system to run it. That's one place where you write or paste a post, approve it, and it goes live. [Should My Business Still Have a Blog?](/jurij/p/should-my-business-still-have-a-blog) covers what that system does. The second bill is the running: a small site runs on a few dollars a month. Hosting, the domain, email and the newsletter tool each cost a little. A [shipping tool](/jurij/p/the-tiny-app-that-eliminated-a-shipping) in daily use for five years ran on about $3 a month. My own site runs under $50 a month, AI tools included. [What Will My App Cost After Launch?](/jurij/p/what-will-my-app-cost-after-launch) breaks that line down. Both bills are easier to carry with a list of what each tool does and costs. That list is the map. ## Hand Over the Setup, Keep the Map Anything that lives online can be handed over. A one-page map keeps it yours to understand. What can go: the setup, the automations, AI, the tools a small team works in, and keeping all of it running. A site on WordPress or a builder counts too, themes and plugins included. Devices, printers and office networks go to a local provider. The decisions [stay with you](/principles/philosophy/client-decides). You name each job in plain words, rank it, and review the result on real work. The accounts stay with you too: every tool on your card, and every helper's access a seat you can remove. [Who Owns the Code My Developer Writes?](/jurij/p/who-owns-the-code-my-developer-writes) has the full list. The map lists every tool: what it does, its login, its monthly cost, when it renews and what connects to what. Then each tool gets a verdict: keep, connect, replace or cut. Whoever picks up the setup later reads the map instead of reverse engineering it. That's the same handover that answers [the bus factor question](/jurij/p/isnt-a-solo-developer-a-bus-factor-of-one). The map matters most on the day something stops working. ## Restore First, Then Find Why When something breaks, get it working, then find the cause. Those are two jobs, and [skipping the second](/principles/diligence/incident-response) is how the same break comes back. Small setups break in familiar ways. A vendor changes its API, a login or a card expires, and the booking emails stop arriving. The worst version is the one a client finds first. So every flow needs an alert [from day one](/principles/diligence/monitor-day-one). Then a failure reaches whoever runs the setup before a client's message does. Basic monitoring is often free, and paid tiers run $20 to $50 a month. Before booking anyone for a fix, it's tempting to ask a chatbot. ## AI Answers How-To, Not Your Account AI explains the tools well. It can't log in and fix your account. A chat assistant is good at how-to: pointing a domain at a site, what a DNS record does, where a setting hides. Use it for that. A free [DNS lookup](/toolkit/dns) then shows where your domain and its email point today. That checks the answer against the real records. So AI replaces part of tech support. Tracing why booking emails stopped needs access to your accounts and the history of what changed. Fixing it needs someone to do the work, and knowing the setup next month needs the map. AI does help inside the setup, on jobs that repeat every week, like the reply each new client gets. [Where Can AI Save My Business Time?](/jurij/p/where-can-ai-save-my-business-time) covers which ones pay back. Someone still traces and fixes, and that person is a bill of its own. ## Who Keeps It Running A small setup's tools stay cheap. The person who keeps them running is where the routes differ. Doing it yourself is free on paper and paid in evenings spent in settings pages. Hourly help is cheaper per call, but each call starts from zero. In October 2026, I sampled a month of tech support jobs on Upwork, most from small businesses. The median hourly budget was $18. A hire means a salary for work that comes in bursts. Hire when the tech work fills a full week, every week. Hours are the wrong unit either way. [Hours measure presence](/principles/philosophy/hours-wrong), not the fix, and an hourly bill grows when a fix goes slowly. ## How I Set Up a One-Person Business My [tech setup](/x/solopreneurs/tech-setup) week starts with the map and fixes what's urgent. Then the map becomes the plan. Each next week sets up more: every tool in the stack, connected so a client is entered once. The map is written for you, and each change comes with its reason. I bring the options and what each would cost; you decide. The tools you already run, I take over where they are. Flows in Zapier or Make I fix in place, or move when the bill outgrows the job. A site on a builder or WordPress I connect to the rest and keep running, and I handle most changes it needs. For deep work past that, I bring in a specialist and stay accountable. New flows go on n8n by default, or on the Zapier or Make you already run. Every flow I build gets an alert, so a failure reaches me before a client's message does. For a one-off break, book a week, and I restore it first. When the work is steady, keep me on by the week, and breaks go first. On your site, whoever built it, small jobs run as tasks on one board. That covers an update, a broken form, a new page or a content edit. I don't bill by the hour. The unit is one week of work, at the price on the [homepage](/), and one fix fits in one week. The other one-week jobs are on the [tech department for small business](/x/solopreneurs) page. ## What the Owner Should Do Now Connect the tools you have before adding one. Then budget for the tools and for the person who keeps them running. For the coach, that means keeping the four tools and adding the client list and one place for automations. Then write the map: every tool, its login, its cost and what it connects to. Once the tools are connected, a booking lands everywhere on its own.