Made for Swiss self-employed & SMEs
A one-person business has no IT department, no budget for pilot projects and nobody to hand the experiment to. That is exactly why a structured start matters more for a Swiss solo self-employed person than for a company with fifty staff: you cannot afford evenings spent on tools that lead nowhere. This 30-day plan moves in weeks, not in one heroic sprint — and every step is tested against your real work, not against a demo.
Why 30 days and not one weekend
Most solo businesses fail with AI for a predictable reason: they try everything in a single evening, get mediocre output, and conclude the technology is overhyped. A month gives you the one thing a weekend cannot — repetition. A workflow only counts if it survives four weeks of real client emails, real invoices and real deadlines.
On cost: start with one paid subscription to a mainstream assistant (typically around CHF 20–30 per month) and nothing else. Ignore every other tool until day 30. The plan is deliberately tool-agnostic; the value is in the routine, not in the brand.
Week 1 (days 1–7): choose one task
Do not start with a tool — start with your time. List every task from last week that took longer than 15 minutes and recurs at least twice a week. For most Swiss one-person businesses the shortlist looks the same: answering routine client emails, writing offers, chasing open invoices, turning meeting notes into next steps.
Pick exactly one. Set up your assistant and do that single task with it every day this week. Nothing else. The goal is to learn what the tool does well on your work, not to build a showcase.
Week 2 (days 8–14): make it sound like you
Writing tasks are where most one-person businesses see the first real gains, because you already know what a good result looks like. Build one reusable prompt template with four parts: who you are and what you offer, the specific task, the tone, and a short sample of text you wrote yourself. The sample does more than any adjective — it is what stops the output from sounding like a machine.
Two rules keep this safe. First: the AI drafts, you decide — never send what you have not read. Second: under the Swiss Data Protection Act (nDSG) you remain responsible for client data, so check where a tool processes and stores data before you paste a client file into it.
Week 3 (days 15–21): add one admin workflow
Now add a second, administrative workflow with a clearly verifiable result: payment reminders, checking invoice details before they go out, or summarising a long document into bullet points. Admin tasks are lower-risk than writing, because errors are visible immediately — a wrong figure in a reminder catches your eye long before the client ever sees it.
Keep a simple list of what you handed over, and note every time the output needed a correction. That list becomes your evidence in week 4.
Week 4 (days 22–30): measure, keep, cut
Honest accounting beats enthusiasm. How much time did the two workflows actually save? Which results needed so much correction that they cost time instead of freeing it? Cut what did not work — that discipline is worth more than any new subscription. Save the prompts that worked into a single file; they are business assets you will reuse for years. Then choose the one workflow you will add next month. Not five.
What this plan will not do
It will not run your business. AI drafts, summarises and checks — you verify, sign and carry the responsibility, contractually and under data protection law. It will also not rescue a messy process: if your invoicing lives in chaos, a language model just produces the chaos faster. Fix the process first, then automate it.
Thirty days, two workflows, one subscription. That is a realistic start — and in a one-person business, realistic is what survives.
