How We Work: Zynra's Async-First Process Explained
No daily standups. No weekly check-in calls unless you want them. Daily commits, clear deliverables, and documentation you can actually use. Here's what working with Zynra looks like.
To get a website made, you do four things in order: decide what kind of site you actually need, choose who builds it (DIY builder, freelancer, boutique studio, or large agency), prepare your content and goals before you contact anyone, then run a simple process — discovery, design, build, content, QA, launch. That's the whole thing. The rest of this guide is the detail that keeps you from overpaying, getting burned, or ending up with a site you don't legally own.
This is the absolute beginner's version. If you're a startup founder raising money and need investor-grade vendor due diligence, read Hiring a Web Studio for Your Startup instead. This one is for the café owner, the dentist, the consultant, the local manufacturer — anyone who has never commissioned a website and wants to do it once, properly.
The phrase "I need a website" hides four very different projects. They cost different amounts, take different timelines, and need different people. Get this wrong and every quote you receive will be meaningless.
Brochure site (the most common, and probably you). A handful of pages that explain who you are, what you offer, and how to contact you. Home, about, services, contact, maybe a blog. No transactions. This is what most small businesses need, and it's the cheapest and fastest thing to build.
Booking site. A brochure site plus a way for people to schedule and pay for appointments — salons, clinics, trainers, restaurants taking reservations. The bulk of the work is integrating a booking tool (Calendly, Cal.com, SimplyBook, OpenTable, or an industry-specific system), not the pages themselves.
Ecommerce site. You sell products online. This is a genuinely different animal: a product catalogue, a cart, a payment processor (Stripe, Shopify Payments), shipping logic, tax handling, inventory. It costs several times more than a brochure site and never stops needing attention.
Web app. Software with logins, user accounts, dashboards, data. A booking platform you operate, a member portal, a SaaS product. This is not a "website" in the brochure sense — it's an engineering project. If this is you, you're past this guide; talk to someone who builds web and mobile apps.
Before you ask for a single quote, write one sentence: "When this site is done, a visitor can ______." If you can't finish that sentence, no one can build the right thing for you.
That sentence is your definition of "done." It also reveals your scope: "...book and pay for an appointment" is a booking site; "...buy a product" is ecommerce; "...understand what we do and email us" is a brochure site, and you can relax — that's the easy one.
There are four routes to a finished website. They are not four quality levels of the same thing — they're different products with different risk profiles. Here's the honest comparison.
| Option | Rough cost (build) | Timeline | Best for | The trade-off |
|---|---|---|---|---|
| DIY website builder (Wix, Squarespace, Webflow, Framer) | €0–€500 + €12–€40/month | A weekend to a few weeks of your own time | Pre-revenue, side projects, people who enjoy it and have time | It's free of money and expensive in hours. Looks templated unless you have an eye. You're the designer, copywriter, and support team. |
| Freelancer (via Malt, Upwork, referral) | €800–€8,000 | 2–6 weeks | A clear, contained brochure or booking site with a defined brief | One person, one set of skills. Great ones are excellent value; the risk is availability, bus factor, and "designer who can't code" (or vice versa). |
| Boutique studio (small senior team) | €2,000–€15,000+ | 3–8 weeks | Businesses that want it done right once, with design + build + strategy from senior people | More than a freelancer, far less than a big agency. You're paying for judgement and a team that won't vanish. |
| Large / full-service agency | €15,000–€100,000+ | 2–6 months | Enterprises, regulated industries, big brand programmes | Process, account managers, layers. You rarely talk to the people actually building. Overkill — and overpriced — for a small business site. |
A few honest notes the comparison table can't hold:
DIY builders are genuinely good now, and we'll say so. A Squarespace or Framer site, built carefully, can look professional and launch this week for the price of a coffee subscription. If you're testing an idea, have no budget, and have a free weekend, do it. We mean that. The catch isn't quality of the tool — it's that the tool can't make the decisions: what to say, what to leave out, what hierarchy converts, which photo isn't generic. That judgement is the actual product when you hire a person.
Freelancers are the natural next step, and the most variable. The top 10% of freelancers are as good as any studio and cheaper. The problem is you can't easily tell from outside, and one person is a single point of failure. Ask what happens if they're sick the week before launch. The good ones have an answer.
Big agencies are usually the wrong tool for a small business. You'll pay for project managers, account managers, and middlemen, and the actual designer will be three people removed from you. That layering exists to coordinate large teams on large budgets. On a five-page site it's just cost.
That's where a boutique studio sits: senior people, no middlemen, you talk to whoever is building. (Yes — that's what we do. We'll still tell you to use Squarespace if that's genuinely the right call for you.)
For the full cost breakdown by tier and the realistic timeline for each route, see How Much Does a Website Cost and How Long Does It Take to Build a Website. And if you're specifically torn between a builder and a designer, Wix vs a Web Designer is the head-to-head.
This is the step everyone skips, and it's the one that determines whether your project is smooth or miserable. The single biggest cause of blown budgets and blown deadlines is not the developer — it's the client who isn't ready and holds up the project for six weeks waiting on copy.
Walk into your first conversation with as much of this as you can. You don't need all of it. Having half of it puts you ahead of 90% of clients.
Gather your copy and your three example sites before anything else. Those two items unblock more of the project than anything money can buy.
If you want to go deeper on writing the brief itself, we wrote a full guide: How to Brief a Web Agency.
Every competent build follows roughly the same six phases. Knowing them means you can tell whether the person you hired is running a real process or improvising.
1. Discovery. A conversation (sometimes a paid workshop) to understand your business, goals, and audience before anyone designs anything. Out of this comes a scope: what's being built, what's not, and ideally a fixed price. If someone quotes a price before understanding your business, that's a flag, not efficiency. (Here's what a good discovery call looks like.)
2. Design. You see how it'll look before it's built — usually as mockups in Figma. You give feedback, typically over one to three rounds. This is the cheapest moment to change your mind, so be honest now rather than after it's coded.
3. Build. The designs become a real, working website. For a brochure site this is often the fastest phase. You usually get a preview link to watch it come together.
4. Content. Final copy, real images, and SEO basics (page titles, descriptions) go in. If you're supplying the copy, this is where your earlier preparation pays off — or where the project stalls if you didn't.
5. QA (quality assurance). Testing on phones, tablets, and desktops; checking every link, every form, every browser; checking load speed. Skipping this is how a form silently stops sending you leads for a month.
6. Launch. The site goes live on your domain, analytics start recording, and you get a handover. A good handover includes logins, documentation, and a walkthrough — not a "you're live, bye."
For brochure and booking sites, expect roughly 3–8 weeks end to end with a freelancer or studio. The delay is almost always content and feedback, not coding. The faster you respond, the faster you launch.
This is the part nobody warns small business owners about, and it's the one that ruins people. You must own and control the five things below in your own accounts. Not the builder's accounts. Yours.
| Asset | What it is | Why it must be yours |
|---|---|---|
| Domain name | yourbusiness.com | This is your address and your brand. If the builder registered it on their account, they can hold your entire web presence hostage. Register it yourself (Namecheap, Cloudflare, Gandi, OVH) and grant them access. |
| Hosting account | Where the site physically lives | If hosting is in their name, leaving them means rebuilding. Have it in your account; pay your own bill. |
| Source code | The actual files of your site | For a custom build, get the code (a GitHub repo you own, or a full export). For a builder like Squarespace, the "code" is the platform account — make sure it's yours. |
| CMS logins | The admin panel where content is edited | You should be able to update your own text and images without paying for every word. Get admin credentials, not "send us the changes." |
| Analytics | Google Analytics / Plausible, etc. | Your traffic data is yours. Set it up under your own account so the history survives any breakup. |
The test is simple: if you fired your builder tomorrow, could you keep your site running and hire someone else by Friday? If the answer is no, you don't own your website — you're renting it from someone who can change the locks.
A reputable freelancer or studio hands all of this over without being asked. If you have to fight for it, you've learned something important about who you hired.
Watch for these. Any one of them isn't automatically disqualifying; two or more is.
If you want a ready-made interview script, Questions to Ask a Web Agency is exactly that.
The cliché answer is "yes, every business needs a website." That's mostly true and slightly useless. The honest version: if your customers find and judge you online before they ever speak to you — and in 2026, they almost all do — then an owned website is the one channel you control completely. Social media is rented land; the platform sets the rules and can change them overnight. We argued this fully in Website vs Social Media. For most businesses the answer is "both, but the website is the foundation."
Short version: a professional brochure site for a small business in 2026 lands somewhere between €1,000 and €5,000 from a freelancer or boutique studio, plus modest ongoing costs (domain ~€12/year, hosting €0–€40/month). A DIY builder is €12–€40/month and your time. Booking and ecommerce sites cost more. Timelines run 3–8 weeks for most brochure and booking sites.
Those are ranges, not quotes — the honest number depends on your scope. We deliberately don't pretend otherwise. For the real breakdown:
Getting a website made isn't technical. It's a series of clear decisions: what kind of site, who builds it, what you prepare, and what you make sure you own. Do those four well and the actual technology takes care of itself. The businesses that get burned almost never get burned by code — they get burned by skipping Step 3 and Step 5.
You don't need to become technical. You need to walk in prepared and walk out owning everything.
Not sure which type of site you need or who should build it? Start a project — tell us about your business and we'll tell you honestly what you need, even if that turns out to be Squarespace. We reply within 48 hours, no funnel.
We take on a small number of projects each quarter. Tell us what you're building.
No daily standups. No weekly check-in calls unless you want them. Daily commits, clear deliverables, and documentation you can actually use. Here's what working with Zynra looks like.
A discovery call isn't a sales call. It's the step that determines whether a project succeeds or fails before a line of code is written. Here's what it covers and why skipping it is expensive.