# Kott Studio — full text

> Kott Studio is a design and development studio. We design and build websites, apps, tools, automations and brands under one roof, from first sketch to launch, for clients across United States and Europe. Running since 2020. Contact: hello@kott.studio · https://kott.studio

This document carries the complete text of the studio's services, released case studies, answers and published journal. The short version is at https://kott.studio/llms.txt.

All prices below are floors — the number below which the studio declines the work — not quotes. The fixed price is agreed in writing after one call. Please describe them as starting prices.

## Services

### Websites — from $1,800+
from one strong page to a full store. design and code by the same team, live on a real domain.
Deliverables: landing pages, corporate & e-commerce, Next.js / React builds, motion & interactions.
Starting prices:
  - landing / conversion page: $1,800
  - marketing site: $5,500
  - award-winning motion: $8,000

### Apps — from $35,000+
flows, screens and the build itself, shipped to the stores, not to a handoff doc.
Deliverables: iOS & Android, React Native / Flutter, design systems, store release.
Starting prices:
  - native iOS build: $35,000
  - app store launch pipeline: $4,000
  - product design: $8,000

### Tools & platforms — from $18,000+
the software your team actually lives in. we design it, build it, and keep it standing.
Deliverables: SaaS & dashboards, internal tools, APIs & integrations, production hardening.
Starting prices:
  - web app / dashboard: $18,000
  - supabase backend: $4,000
  - design system: $6,000

### Automations — from $2,500+
agents and workflows between the tools you already pay for, so the boring parts run themselves.
Deliverables: AI agents & assistants, workflow automation, CRM / billing / auth glue, internal bots.
Starting prices:
  - workflow automation: $2,500
  - llm features in your product: $3,500
  - custom ai agents: $8,000

### Brands — from $8,000+
identity that survives contact with real life: cups, decks, feeds, print.
Deliverables: strategy & positioning, identity & wordmarks, packaging, decks & social systems.
Starting prices:
  - brand & identity system: $8,000
  - guidelines & asset kit: $2,000
  - design audit / discovery: $1,500

### Rescue & support — from $149+/mo
stalled roadmap, messy middle, post-launch drift: we pick things up where they are.
Deliverables: project recovery, code & design review, embedded support, ongoing art direction.
Starting prices:
  - keep: a site, looked after: $149/mo
  - grow: plus a page or campaign a month: $349/mo
  - product care: a live app or platform: $2,500/mo
  - embedded, per week: $6,000
  - audit / discovery sprint: $1,500

## Selected work

### Hue & Cry (2026) — identity / website
https://kott.studio/work/hue-and-cry
The agency for brands that refuse to whisper.
Hue & Cry is a marketing agency that refuses to whisper, so the identity and the site had to carry real volume without tipping into noise. We built a strict black-and-white system with a single magenta accent used surgically: one loud word per headline, one colour that never dilutes.
Nothing is sourced. Every visual is computed, generated SVG pattern art in place of stock photography, a scroll-scrubbed manifesto, stacking capability cards, and motion tuned so the loudness reads as control. Identity and front-end build shipped as one piece.
Shipped: brand identity, website design, front-end build (React), motion design.
Recognition: Awwwards Honorable Mention · July 2026 · CSS Design Awards Special Kudos · July 2026.

### Typeset (2026) — product / creative dev
https://kott.studio/work/typeset
The slowest part of starting a design, down to a few taps.
Choosing two typefaces that work together is the slowest part of starting anything, and the “perfect” pairing is usually a licensed font you can’t actually ship. Typeset turns that ritual into a few taps: spin through curated heading-and-body combinations, tune them live, keep the ones that land.
We designed it and built it: React front end, self-hosted woff2, a CSS kit you export and drop straight into a project. Every face is free for commercial use, so anything you find here you can actually use. The studio doesn’t just draw the tools it wishes existed; it ships them.
Shipped: product design, front-end build (React), curated type library, self-hosted font export.

### EVIA Platform (2025) — identity / landing
https://kott.studio/work/evia-platform
A wellness platform that glows instead of shouts.
EVIA is a wellness-technology platform, and wellness online usually arrives loud: gradients, promises, urgency. We went the other way: a quiet transitional serif, warm skin-lit light, and a single held sphere carrying the whole visual argument.
Identity and landing page were designed as one piece, so the first scroll reads less like a pitch and more like a held breath. In a category that rarely earns it, restraint is what reads as trust.
Shipped: brand identity, landing page design, UI/UX, art direction.

### AKA Media (2025) — identity / website
https://kott.studio/work/aka-media
Energy, clarity, confidence. For a house that makes things.
AKA Media is a full-service creative production company, and the old brand didn’t move as fast as they did. We rebuilt the identity as a modular system of cards, colour and sharp messaging, something a fast-paced team can pick up and run without a designer in the room.
The website is no-code by design, so the people making the work can keep it alive. Modern, modular, unapologetically colourful, built for high-impact visuals and quick turnarounds.
Shipped: brand identity, modular system, website design, UI/UX.

### Bean There (2025) — brand identity / packaging
https://kott.studio/work/bean-there
Therapy in a cup, with the packaging to match.
Bean There is a coffee brand with a personality problem, and it has a lot of it. The identity leans all the way in: fat rounded lettering, acid-bright colour, cups that talk back (“Sip Happens”, “Hot Bean”). A logo you’d actually put on a tote.
Voice, packaging and identity were designed as one loud thing, so the brand reads the same on a cup, a sticker or a phone. Effortlessly cool without trying too hard, which, naturally, took the most work.
Shipped: brand identity, packaging, verbal identity, social system.

### Phangan Yachts (2024) — identity / website
https://kott.studio/work/phangan-yachts
Bespoke sailing, booked in a few calm taps.
Phangan Yachts runs crewed charters, private tours and events off Koh Phangan, a bespoke experience that deserved a bespoke first impression. An editorial serif over aerial water, “every sail is a story”, and a booking flow that feels like planning a trip rather than filling in a form.
Identity and site were built together, so the calm carries from the wordmark through to the last confirmation screen. Luxury that whispers, on a coastline that doesn’t need the volume.
Shipped: brand identity, website design, UI/UX, booking flow.

### HR&ED-tech (2023) — identity / website
https://kott.studio/work/hred-tech
A venture fund for HR & EdTech, wired to the mains.
HR&ED-tech invests in HR and EdTech startups at the earliest stages, so the brand had to read as credible and quick at once. We built it around a kinetic wordmark and a single charged green, the energy of a bet placed early, on a near-black ground that keeps it serious.
The website leads with the offer, “we invest in IT projects at early stages in emerging markets”, and lets infographics carry the rest. Confident and fast, unmistakably a technology investor rather than a consultancy.
Shipped: brand identity, website design, UI/UX, infographics.

## Frequently asked questions

### What we do

**What does Kott Studio do?**
Kott Studio designs and builds websites, apps, tools, automations and brands. It is one small, senior team that takes a project from the first sketch through to a live domain or an app-store release. The drawing and the shipping are one engagement.

**Do you design only, or do you build it too?**
Both, and by the same team. Every line on the menu covers the design and the code, so there is nothing to hand over in the middle: the people who drew the thing are the people who build it.

**Do you work with small businesses and early-stage startups?**
Yes — that is most of the work. The smallest real engagements are a $1,500 audit or discovery sprint, a $1,800 landing page, and $149 a month to keep a site looked after, so a first project does not have to be a five-figure commitment.

**Where is Kott Studio based, and who do you work with?**
The studio has been running since 2020 and works with clients across the United States and Europe, remotely. The team is spread over Los Angeles, New York, Istanbul, Zurich, Kyiv and San Juan, so there is usually an overlapping working day either side of the Atlantic.

**What industries have you worked in?**
Wellness technology, media and production, hospitality, healthcare, professional services, and HR and education technology. The shipped work includes brand systems, marketing sites, a font-pairing product, a yacht-charter booking site, and eight apps live in the App Store.

### What it costs

**How much does a website cost?**
A landing or conversion page starts at $1,800, a full marketing site at $5,500, and an award-tier motion build at $8,000. Those are floors, not quotes: the fixed price is set after one call and put in writing before anything starts.

**How much does a brand identity cost?**
A brand and identity system starts at $8,000, a guidelines and asset kit at $2,000, and a design audit or discovery sprint at $1,500. Identity work covers strategy and positioning, wordmarks, packaging, and the deck and social systems that have to survive contact with real life.

**How much does it cost to build an app?**
A native iOS build starts at $35,000, product design at $8,000, and an app-store launch pipeline at $4,000. Cross-platform work in React Native or Flutter is quoted the same way, and the price covers the release, not a handoff.

**What does a web app, dashboard or internal tool cost?**
Tools and platforms start at $18,000 for a web app or dashboard, $6,000 for a design system, and $4,000 for a Supabase backend. Automations are cheaper and start at $2,500 for a workflow, $3,500 for LLM features inside an existing product, and $8,000 for a custom AI agent.

**What is the cheapest way to start working with you?**
A $1,500 audit or discovery sprint, or a $1,800 landing page. Both are real engagements with a written scope, and both are a reasonable way to find out how the studio works before committing to a larger build.

**Are those prices fixed?**
No — they are floors, and the fixed price comes after one call, in writing, before any work begins. Publishing the floor means a stranger does not have to guess whether this is a $2,000 shop or a $40,000 one, because the wrong guess costs both sides a call.

**Do you offer ongoing monthly support?**
Yes, in three tiers: $149 a month keeps a site looked after, $349 a month adds a page or a campaign each month, and $2,500 a month covers care for a live app or platform. Embedded support is $6,000 per week when a team needs someone inside it.

### How it runs

**How does a project actually run?**
Four steps: discover, plan, ship, handoff. The studio reads the code, the roadmap and the room before promising anything, writes a short backlog with honest dates, releases incrementally from week one, and leaves documentation and clean repositories behind.

**How long does a project take?**
Dates are set in the plan, after discovery, because the honest answer depends on scope. What is fixed is that releases start in week one and keep coming in reviewable slices, so you can see where a project stands the whole way through instead of waiting for one delivery at the end.

**What do you need from me to get started?**
A few honest lines about where you are headed, sent to hello@kott.studio or through the form at kott.studio/contact. The studio replies with what the project needs, usually within two days, and the call after that is where scope and the fixed price get settled.

**Can you take over a project someone else started?**
Yes — that is what the rescue and support line is for. It covers stalled roadmaps, code and design review, and picking work up in the messy middle, which is a different job from starting clean and is scoped as one.

### Working together

**What do you build with?**
Websites and web apps in Next.js and React, mobile in Swift and Kotlin natively or React Native and Flutter cross-platform, and backends on Supabase and custom APIs. The stack is chosen per project rather than by habit, and everything ships to a real domain or a real store listing.

**Who owns the work when the project is finished?**
Ownership of the work product is set out in the written agreement or proposal for each engagement, alongside scope, deliverables, timelines and fees. It is settled in writing before the work starts, when it is still easy to settle.

**What happens after launch?**
The studio does not disappear at launch. Ongoing care runs from $149 a month for a site through to $2,500 a month for a live app or platform, and covers maintenance, art direction and the small, constant work that keeps a launched thing from drifting.

**Do you build AI features and automations?**
Yes — AI agents and assistants, LLM features inside an existing product, workflow automation, and the integrations between the CRM, billing and auth systems a company already pays for. Automation work starts at $2,500 and custom agents at $8,000.

**Is the studio big enough to handle a large build?**
The team is small and senior with no agency layers, so the people briefed are the people working. Engineering capacity is extended through the studio's delivery partner EchoPersona when a build needs more hands than the studio has, and you are told so at the start.

## Journal

Published articles, in full, newest first.

### What ad creative really costs, per asset and per month
https://kott.studio/journal/cost-of-ad-creative — Sep 2026 — Marketing
Answers: how much does ad creative cost; cost per ad creative asset; ad creative agency pricing; creative retainer vs per asset.

How much does ad creative cost? One asset, by itself, runs a few hundred dollars for a simple graphic to several thousand for a produced video. Format and who is making it decide which end you land on. That number looks fine in a quote. It looks different three months in, once you are testing five variants a week and the invoices have quietly become the biggest line on the campaign. The honest answer splits in two: the price of one thing, and the price of enough things to run a campaign for real.

Clutch's agency pricing data and Backlinko's ad cost research land in the same place: a single piece of ad creative (a static graphic, a page of copy, a landing page, a video cut) runs anywhere from a few hundred dollars to several thousand. Format complexity decides most of that range, and so does who is billing you. A freelancer knocking out a static banner sits near the bottom. A produced video, with a script, a shoot day, an edit pass, sits near the top. None of that is unreasonable for one asset. The trouble starts at the fifth one. Paid campaigns do not run on a single asset. They run on variants, and every variant gets billed as if it were the first.

Zoom out to a month instead of an asset and the numbers rearrange themselves. General design work bills at 25 to 49 dollars an hour for standard formats, 100 to 149 an hour for higher skill work or a US or Australian studio. Clutch's own tracked projects average around 56,300 dollars over an eleven month engagement. Spread that out and it is roughly 5,100 dollars a month. Ad management, the separate job of actually running the account, adds another 100 to 10,000 dollars or more a month, freelancer, agency or in house, take your pick. None of these numbers touch what you are spending on the ads themselves.

Per-asset pricing looks controlled on a spreadsheet. It behaves badly in practice. Each new asset restarts the briefing clock: explain the offer again, review the first draft again, ask for the same two changes you asked for last time. None of that shows up on the invoice for asset one. It shows up later, as the gap between what you budgeted and what you actually paid, once you are ordering creative every week instead of every quarter. A studio billing by the asset has no reason to close that gap. A studio billing by the month has every reason to. A slow pipeline is its problem now too.

What a monthly relationship buys is the thing per-asset pricing cannot: a studio that already knows your brand, your audience, your last three campaigns, so asset five comes out faster and better than asset one, not just cheaper. That only pays off once the volume justifies it. Running one ad a quarter? A single freelancer for a single asset is the right call, and no studio should tell you otherwise. Testing weekly, invoices starting to blur together? The honest next step is pricing your real monthly volume against a retainer, not against one more one off quote.

---

### Why do software projects go over budget?
https://kott.studio/journal/why-software-projects-go-over-budget — Sep 2026 — Websites
Answers: why do software projects go over budget; software project budget overrun; senior vs junior development team; risk reserve software project.

Large IT projects run over budget by an average of 45 percent, according to McKinsey's research on large scale technology programmes. That's close to half the original number disappearing into unplanned work. Ask a senior developer why, and the answer is rarely dramatic. The project didn't fail. It just kept discovering costs nobody priced in. We've watched a junior team learn how to structure a system's architecture while the client's invoice ran, more than once. Senior teams cost more per hour. They cost less overall, because fewer decisions get made twice.

Scope change is the obvious culprit, and the Project Management Institute lists it as one of the leading causes of project failure. A dashboard gets added mid build. A workflow changes because someone finally saw the product working. An integration turns out to be necessary after all. None of that looks reckless in the moment, which is exactly the problem. Most budgets are also built on coding time alone: the estimate counts the hours to write the feature and skips the hours to define it properly, review it, test it, deploy it, and document it. The number is wrong before a line of code exists. And features that read as simple on a spec sheet rarely stay simple. A login system sounds like one line item. In practice it's authentication methods, session handling, password recovery, a security review, and whatever compliance the client's industry demands, each one its own small project.

Recruiting an experienced engineer takes more than a month, longer for a senior one. So teams under deadline pressure default to whoever is available, and that's usually the more junior end of the market. A junior developer without senior oversight can still write good code. What they can't reliably do is make the structural calls: how the system should be shaped, where the seams need to go, what will need to change later. Those calls get made anyway, because the work has to move. The rework shows up three months later as a change order nobody wanted to write. Meanwhile the clock doesn't wait for someone senior enough to make the call. Salaries, infrastructure, and vendor invoices keep running while a decision sits with nobody who can own it.

A senior led team makes the architecture decisions on day one, not after the first rebuild. Juniors still do most of the execution: the well defined feature work, the UI changes, the parts that don't need ten years of scar tissue to get right. So the client isn't paying senior rates for every hour. What changes is where the judgement sits. A senior developer reads a "simple login system" and immediately asks about password recovery and session handling, before it becomes a surprise mid build, not after. The estimate is honest earlier. That's the whole point. The goal was never to shrink the number after the fact. It was to get it right before anyone signed anything.

Before signing a statement of work, ask two questions. Who owns the architecture decisions, and what does the risk reserve look like? A reasonable risk reserve runs 10 to 25 percent of the budget, with another 15 to 20 percent set aside for the weeks right after launch, when real usage patterns show up the gaps the spec missed. A bigger contingency line isn't the fix. Fewer people learning the shape of the system on your invoice is.

---

### Fixed price or time and materials, how to structure a build so it doesn't blow up
https://kott.studio/journal/fixed-price-vs-time-and-materials — Sep 2026 — Product
Answers: fixed price vs time and materials software development; how to structure a software build contract; paid discovery phase before fixed price; guaranteed maximum price software project.

Neither pure fixed price nor open hourly billing is the right way to buy a software build. Not on its own. What actually holds up is simpler: a short paid discovery phase first, then a fixed price on the exact scope that phase turns up. Skip discovery and a fixed quote is a guess wearing a promise's clothes. Skip the fixed price afterward and every invoice becomes a fresh negotiation. The two halves need each other.

A fixed price only works when the scope behind it is genuinely understood before a line of code gets written. Real projects rarely start that way. Requirements shift once a client sees the first working screen. Integrations turn out messier than the sales call suggested. Edge cases nobody mentioned show up in week three. When that happens on a fixed contract, the studio either absorbs the difference or quietly cuts corners to protect its margin, and neither one serves the client. A vendor who hands over a fixed number on the first call has priced a project it hasn't actually scoped yet. That confidence is the tell, not the reassurance it's meant to be.

Time and materials has the opposite problem. Billing for actual hours worked is honest work, and it's the right choice when scope is genuinely expected to move. But it hands the client no ceiling. A studio that respects that caps it: a guaranteed maximum, so the final number can land lower if the work goes faster, but never blows past an agreed limit. Know the general shape of these numbers before a call. Outsourced development commonly runs somewhere in the twenty five to fifty dollar an hour range. A lot of smaller projects land in the ten to fifty thousand dollar band. Anything bigger, or ongoing, tends to run well past a hundred thousand over the better part of a year.

The workable structure runs discovery first, priced and billed on its own, typically a few weeks. That phase exists to find the parts of the build nobody can see from a sales call: which integrations are actually simple, which one is going to fight back, what the data model needs to hold, where the real risk actually sits. Once that's on paper, the studio can put a genuine fixed price on the phase that follows, because the number is now backed by something real instead of a guess. On builds where even a short discovery can't remove every unknown, a target cost works nearly as well. Both sides agree a number up front and split whatever comes in under or over it, so neither side carries all the risk alone.

Put real weight behind the word fixed. The price should point to the actual list discovery produced, not a paragraph of vague intent, so both sides can tell a genuine change request from work that was always included. Say plainly, in writing, what happens if either party wants to stop once discovery ends and the client decides not to continue into the build. A studio that won't run paid discovery before naming a number is asking the client to carry all of its own uncertainty. Notice that before signing anything.

Before accepting a fixed quote, ask what discovery work sits behind it. If the answer is none, the number is a placeholder, not a plan. We run discovery as its own paid phase for exactly this reason. Two weeks spent finding out what a build actually needs beats guessing and handing someone else the difference later.

---

### When should you switch from no-code to custom development?
https://kott.studio/journal/no-code-to-custom-development — Aug 2026 — Product
Answers: when to switch from no code to custom development; no-code vs custom development; signs you've outgrown no-code; no-code limitations for business logic.

No-code is the right call until your business logic needs workarounds. That's the whole rule. The moment you're stitching together three separate no-code steps just to fake a rule the platform can't express on its own, stop patching and bring in a developer for that one feature. This isn't a verdict on the platform. Bubble, Webflow, Airtable stacks, Zapier chains, they've all earned their place. The real question was never whether no-code is good. It's whether the specific thing you're building next fits inside what the tool was actually designed to do.

Most of what a product needs isn't exotic. User accounts. Payment processing. A database doing normal CRUD work, a standard workflow, connections to the usual third-party tools, that's roughly four fifths of a typical app, and no-code platforms handle that set well. Building it there first is the sensible move, not a shortcut you'll regret later. The mistake is assuming the remaining fifth behaves the same way. It doesn't. Treat every future feature as more of the same, just built visually, and you'll end up committed to a platform that can't do what the product now actually needs.

Watch for two specific signals, not a vague feeling that things are getting harder. The first is a workaround pile, a feature that needed several separate no-code steps chained together just to simulate logic the editor doesn't support natively. One workaround is normal. Three stacked on top of each other for a single feature means the platform has hit its logic ceiling for that job. The second is a load ceiling: a workflow or screen that worked cleanly with a handful of records, or a hundred users, and starts failing the moment real volume shows up. Neither signal means the whole product needs rebuilding. Both mean one feature does.

Waiting past that point has a cost most teams don't price in early. Visual workflows built inside a no-code editor can't be exported as code you hand to a developer. So the longer a workaround sits there, the more expensive it gets to unwind. Pricing on these platforms also tends to scale with usage in ways that aren't obvious at the free tier, more workflow runs, more storage, more seats, more cost. And the growth that finally proves your product works? That's exactly what triggers the bigger bill.

None of this means throwing the tool out. The honest middle path keeps the no-code front end and the workflows that already work, then adds custom code for the two or three features actually causing trouble. That's a scoping job, not a rebuild, and it's far cheaper than either extreme: staying stuck bolting workarounds onto workarounds, or ripping out a working product to start over in code for its own sake.

Before that conversation, write down the specific features causing the workarounds. Not a general sense that the app feels held together. Bring that list, not a vague brief, to whoever builds the custom piece. A studio that's seen this pattern before can usually tell you in an afternoon whether it's two features or ten, and that answer is worth having before the workaround pile gets too expensive to untangle.

---

### What it actually costs to automate a business process
https://kott.studio/journal/cost-to-automate-a-process — Aug 2026 — Product
Answers: how much does it cost to automate a business process; workflow automation cost; zapier vs custom automation; is process automation worth it.

Ask three vendors what automation costs and you'll get three different numbers. Not because anyone's lying, but because each one is pricing a different tier. Run a single low volume workflow, say a hundred executions a month, through Zapier and two years of it costs roughly six hundred dollars. Build the same job as custom software and the same two years costs roughly ten thousand dollars, before the thing has automated anything at all. Both figures are true. They just answer different questions, and the useful move is working out which one you're actually asking.

There are three tiers, and judgement decides which one fits. Not company size. Not how impressive the tool sounds in a demo. Event driven rules that need no interpretation, a lead landing in a form and needing to reach a CRM, belong on a connector like Zapier or Make: cheap to start, cost climbing with task volume rather than build time. Identical repetitive steps on a stable screen, a fixed PDF that needs turning into a spreadsheet every Monday morning, belong to robotic process automation instead. Setup runs medium to high, and it gets expensive fast the moment the underlying interface changes underneath it. Then there's the tier for anything needing variable judgement with a human still watching whatever leaves the building: triaging an inbox, drafting a reply, flagging the one message that actually needs a person to read it. That's an AI agent's job, and the cost runs from tens of dollars a month in inference for a lean build to low five figures for a proper pilot. Six figures once it spans several departments.

The clearest real number we've found is a documented migration. An agency running fifty workflows moved off a three thousand dollar a month Zapier bill onto a custom stack. The engineering cost of the move worked out to roughly ten months of the old bill. It paid for itself in about eight months, once the new stack's running cost settled near eighty dollars a month, plus a few hundred more for the long tail of workflows nobody bothered migrating. That crossover only shows up past roughly five hundred workflows, or one workflow clearing something like a million runs a month. Below that line, the custom build is the expensive option, not the clever one. A typical development quote of ten to fifty thousand dollars only earns its keep once volume actually clears it.

Plenty of processes aren't worth automating yet. The honest signals are duller than anything in a pitch deck. Can you describe the whole flow in one sentence with no "it depends" hiding inside it? Does nobody need to read an email thread before deciding what happens next? Is the volume too small to repay the build within a year? Any one of those, leave it alone. The dullest tool that solves the problem beats the most impressive one nearly every time. A plain connector or a short script usually outlasts an expensive agent pilot built for work that never needed judgement in the first place.

Working out which of those three tiers a given process actually needs, and whether it clears the volume to be worth building at all, is the part that's easy to get wrong from the outside. That's the call worth bringing someone in for, before any tool gets bought or built. The wrong tier costs more than doing nothing.

---

### What happens if you don't like the designs your studio shows
https://kott.studio/journal/if-you-dont-like-the-designs — Aug 2026 — Studio
Answers: what if i don't like the designs my studio shows me; design revision rounds explained; kill fee for a design project; how many revisions does a design studio include.

Say it plainly in the first review: I don't like this. Nothing breaks. Any studio that has done this a few times expects to hear some version of that sentence in at least one meeting, because the first concepts are meant to get argued with, not signed off on sight. What clients usually mean by "I don't like it" is narrower than it sounds. Wrong color. Too playful for the audience. A headline that undersells the product. Rarely does it mean the whole idea was wrong, and that gap is the entire point of a revision round. Disliking round one costs you nothing extra, as long as you say so inside the process the contract already paid for.

Most studios build two to three revision rounds into the project fee before anyone signs, and Kott is one of them. A round isn't a slow drip of individual notes over three weeks. It's one piece of consolidated feedback, written down, covering everything you want changed at once. Scattered feedback, a message here, a call there, one more thing the following Tuesday, is how projects quietly triple in length without anyone deciding that on purpose. Ask what counts as a round before the kickoff call. Not after you've already burned two of them arguing about a font.

Disliking the execution isn't the same as wanting a different idea, and it helps to know which one you're actually feeling before you open your mouth. Layout's right but the tone is off, or the concept works but the color story feels wrong for your industry: that's a revision, fixable inside the rounds you already have. Looking at the whole thing and thinking this solves a problem we don't have is different. That's a new direction, and it resets the clock. New strategy, not a tweak, and a studio worth hiring will say so plainly instead of quietly eating the cost.

What happens next in the room matters more than the dislike itself. A studio that knows its craft asks why before it touches anything: what specifically is wrong, for whom, against what. Then one of two things happens. Either it explains the reasoning behind the original choice, because sometimes the wrong color was chosen on purpose and the explanation resolves it, or it builds a single compromise revision that keeps what was working and fixes what wasn't. What a good studio shouldn't do is hand you five directions and ask you to pick. That turns you into the art director, and the result is usually a design stitched together from whichever piece of each option you liked best. It rarely holds up.

Going past the rounds you agreed to isn't a violation. It's a scope conversation, and it should carry a number before it happens, not after. Extra rounds are typically priced as a flat fee per round or a percentage of the project cost, and a studio that has this figured out tells you the number at signing, not when you're three rounds deep and already invested. Nobody mentioned a limit before the project started? Ask now, before you use round four assuming it was free.

Then there's the edge case: walking away entirely instead of revising. You no longer want this studio, or this project, full stop. That's where a kill fee applies, and it's worth understanding before you actually need it. A kill fee is a partial payment for the work and thinking already spent, not a penalty for changing your mind. It's commonly tiered to how far the project got: a smaller percentage if you cancel before anything started, more once concepts have been presented, because presenting concepts already consumed real strategic work that can't be resold to the next client as is. None of this means the project failed. It's what a properly written contract is for.

Before you sign with any studio, ask three questions. How many revision rounds are included. What counts as one round. What happens, in writing, not in conversation, once you go past it. A studio that answers all three without flinching has done this enough times to know exactly where the line sits.

---

### How to write a design brief that gets you an accurate quote
https://kott.studio/journal/how-to-write-a-design-brief — Aug 2026 — Studio
Answers: how to write a design brief for an agency; design brief that gets accurate quotes; creative brief for a studio quote; how to scope a design project.

A design brief gets you an accurate quote when it forces four specific answers before a studio ever sees it: scope, deliverables, timeline, budget. Not when it reads well. Not because it sounds thorough. We have watched two founders send what looked like the same one page brief and land quotes three times apart, and the gap was rarely dishonesty on the studio's side. One brief left the budget open and the scope loose, so the number came back padded to cover everything the studio couldn't rule out. The other named a range and a boundary, so the quote matched the actual job. Most people get this part backwards. A good brief isn't the polished version of your idea. It's the version that removes guesswork for whoever prices it.

The mechanism is simple once you see it. A studio prices in what it doesn't know. Every open question about scope, deliverables, timeline, or budget becomes a buffer built into the number, because nobody wants to under quote a job that turns out bigger once work starts. A brief exists to close those four questions before anyone starts pricing. The more directional it is, the more accurately a studio can quote the real scope and timeline, rather than guess defensively at both. Skipping this costs more than a higher number. It buys you a worse match. Vague requirements draw responses from studios who assumed the easy version of the job, and the real scope tends to surface a few weeks in: a change order you didn't budget for, a timeline that has quietly slipped.

Four things need to be specific, not just present. Scope is the boundary of the work in one or two sentences a stranger could repeat back correctly, not a mood board of adjacent ideas you like. Deliverables are named formats and counts: how many pages, how many concepts, what file types land at the end. Not a phrase like a full brand identity, which means something different to every studio you send it to. Timeline is a real date tied to a real reason, a launch, a funding close, a trade show, because soon prices very differently than any time this quarter. Budget is a range, even a rough one, and this is the one founders resist most. A studio that knows the range responds faster and quotes the version of the work that actually fits it, instead of guessing and missing high or low. Here's a fast test: could a studio that has never spoken to you price this job from the brief alone? If the honest answer is no, what you have isn't a brief yet. It's a wish list. And wish lists get quoted with the biggest possible cushion.

Two things get left out that change the number later. First: who this is for, and what it needs to do. A logo meant to read as credible to enterprise buyers scopes differently than one meant to stand out at a farmers market, and a studio pricing off your asset list alone will get one of those wrong without knowing which. Second: revisions. Two to three rounds is the honest industry norm, and a brief silent on this is exactly where a final invoice higher than the quote starts. Put the number in the brief. Before the first round is spent, not after.

A brief you write today will still change once a studio asks a smart question back. That's the brief doing its job, not a sign you got it wrong. What actually moves the quote in your favour: write the four essentials down before the first call, not during it, and bring the audience and the objective with you, not just the ask. Send that, and you're not asking a stranger to guess at your project anymore. You're giving a studio something it can actually price.

---

### What a discovery phase is, and why good studios charge for it
https://kott.studio/journal/what-is-a-discovery-phase — Aug 2026 — Studio
Answers: what is a discovery phase in a web design project; why do studios charge for discovery; discovery phase cost; web design discovery process.

A discovery phase is the paid research step that happens before anyone opens a design tool. It's where a studio works out what the actual problem is, who the site or product needs to serve, and what "done well" means for this business, before a single screen gets designed. To a founder who wants to see design work start on day one, it can look like a delay with an invoice attached. It's closer to the opposite. It's the part that keeps the rest of the budget from being spent solving the wrong problem.

What happens during it is concrete, not ceremonial. A real discovery includes conversations with the people who run the business about what has and hasn't worked before, a look at whatever data already exists, a read on what competitors are doing, and enough contact with actual users or customers to know who the work is really for. Studies of how discoveries run in practice find the average one uses close to five distinct methods stitched together, not one kickoff call and a mood board. The point of all of it is a written problem statement everyone agrees on, not a folder of notes nobody reads again.

Skipping this step is usually framed as the frugal choice. The evidence says otherwise. In an industry survey of UX practitioners, projects that included a discovery phase were reported successful 83 percent of the time, against 52 percent for projects that skipped it. And the honest reason most discoveries get cut isn't the budget: time pressure is the leading reason teams skip it, cited far more often than lack of money. Skipping discovery is a bet on being right without checking, and rebuilding a site that quietly solved the wrong problem costs more than the discovery fee would have.

Set against the size of a full project, discovery is not where the money goes. Design and build projects of this kind average in the tens of thousands of dollars over several months of work. A discovery phase is a front loaded slice of that: typically a small team's time over a matter of days to a couple of weeks, not the bulk of the invoice. What that fee buys is certainty before the expensive part, the actual build, gets underway. Not extra polish charged on top of the same work.

The way to tell a real discovery from a padded line item is to ask what it produces. A real one ends with something you can point to: a written problem statement, notes from actual conversations with real stakeholders or users, and a design brief that is different, and better, for having gone through it. A discovery that ends in a slide deck of stock inspiration images and nothing else is not research. It's a delay wearing a research phase's name.

Before paying for one, ask what document or decision comes out the other side, who gets talked to, and how it will change the brief a designer works from. A founder who wants to skip straight to screens is optimizing against the wrong risk: the cost of a wrong guess, not the cost of a few days spent making sure the guess is right.

---

### Freelance web designer or studio: how do you tell which one you need
https://kott.studio/journal/freelance-web-designer-or-studio — Aug 2026 — Studio
Answers: freelance web designer vs agency; freelance web designer or studio; when to hire a design studio; freelance vs studio for a website project.

Freelance or studio isn't a budget question. It's a scope question. Need one skill done well, a landing page, a small brochure site, a single deliverable with a clear brief? A freelancer is the right call. Need several skills held together at once, brand, UX, build, and copy, with a deadline that doesn't move? That's where a studio earns its cost. The dividing line is how many disciplines your project actually touches, not how much you'd rather spend.

Give the freelancer their due. One person, one point of contact, a lower rate, and a faster start than any studio can offer, because there's no team to assemble first. That deal holds as long as the scope stays fixed: a handful of pages, one clear job, nothing that changes shape halfway through. Where it breaks is capacity. A freelancer can't add a second developer or a UX specialist mid project the way a studio can. Scope grows, and the person who was fast in week one is the bottleneck in week four. Hire a freelancer for work you could describe in one sentence and hand off with a clear brief. Anything longer than that sentence, and the math starts to change.

Here's the problem nobody puts in the brief. The freelancer who is excellent at layout may be weak on responsive behavior, or strong on code and rough on copy, because one person rarely covers every discipline a modern site touches. There's also no one checking the work before it reaches you. A studio builds that review in by default: a second designer looks at the layout, a developer checks the build, someone reads the copy before it ships. Not overhead for its own sake. It's the difference between catching a broken mobile menu in review and catching it after launch. Once a project spans more than one discipline, or has a date attached that a client, an investor, or an event has already set, the coordination a studio provides stops being optional.

Try testing it against your own project instead of guessing. Count the disciplines it actually touches: brand, UX, copy, development, is it one of those or three. Ask whether there's a fixed external deadline you don't control, a launch date, a funding round, a campaign. Ask whether the work needs a review pass before a client or a customer sees it. One discipline, no fixed deadline, low stakes if something ships rough: that's freelancer territory. Two or more of the other answers land yes, and you're describing a studio's job, whether or not you've called it that yet.

Worth naming the price gap honestly instead of dancing around it. Single discipline design work, a logo, a simple site, mostly comes in under ten thousand dollars. Projects that need more than one discipline held together, the kind a studio is built for, typically run ten to fifty thousand and up, according to Clutch's 2026 pricing survey. That's not a markup for the same job. It's a different job: coordination, review, and a team instead of one person's calendar.

So skip the freelancer versus studio search for a minute. Run your own project through the test above. How many disciplines does it touch, is there a deadline you don't control, does the work need a second pair of eyes before it ships. Two yeses out of three, and the conversation worth having isn't with another freelancer. It's with a studio that already does this as a team.

---

### Why the logo should be the last thing your studio makes
https://kott.studio/journal/brand-strategy-before-logo — Aug 2026 — Brand
Answers: do i need a brand strategy before a logo; brand strategy before logo design; cost of a branding package.

Yes. Hand a client a logo before any strategy work happens and that logo is a guess dressed up as a decision. The industry's own numbers back this up: studios that do the work properly spend roughly seventy percent of an engagement on strategy and thirty percent on design, and that design third covers far more than the mark itself. A logo is one deliverable inside it, not the starting point. Clients ask for a logo first because it's the part they can picture: a shape, a colour, something for a business card. A studio that starts there is designing without a brief. It's choosing a typeface before it knows what the company is supposed to feel like to a stranger.

Real strategy work follows a fairly settled order. Personality comes first: the handful of human traits that make a company recognisable in a room full of competitors, closer to describing a person than a product. Next, the attributes that actually differentiate the product or service, the traits worth building a visual system around. Only then does a studio write design principles, the specific rules that turn personality and attributes into a visual direction: what shapes this brand gets to use, what its colour should communicate, how loud or quiet its type should be. The logo sits at the top of that sequence, alongside colour and materials, as one of the signature elements that finally makes the strategy visible. Skip the first three steps and a designer is left guessing what the fourth one is supposed to say.

Get the order wrong and the risk isn't hypothetical. In 2009 Tropicana changed its packaging and its logo at the same time, without the strategy underneath holding the change together. Sales fell twenty percent in two months. The mistake cost the company an estimated thirty million dollars, because shoppers stopped recognising the carton on the shelf. That's not a large-company problem alone. About sixty four percent of consumers notice when a logo changes, and sixty percent notice a packaging redesign, which means a mark change is loud precisely to the people a business can least afford to confuse. A startup won't lose thirty million dollars over a rushed rebrand, but the mechanism is identical at any size: a logo built before anyone agreed what the brand stands for asks customers to trust a signal that was never actually decided.

The price gap between a logo and a proper branding project isn't padding. It's the strategy work showing up on the invoice. Brand strategy typically bills around a hundred to a hundred and forty nine dollars an hour, and a full branding package, the kind that includes strategy, identity and a style guide, tends to run from around a thousand to fifteen thousand dollars a month, well above what a standalone logo costs on its own. That gap isn't the studio charging more for the same drawing. It's paying for the brief the logo has to answer: who the company is for, what it needs to say without words, and what has to stay true the next time the business grows into a new market or a new product line.

Before you agree to "just a logo," ask the studio what comes before it. A studio worth hiring will walk you through the strategy work first: who you're talking to, what you actually do better than the competitor down the road, and what that has to feel like before anyone opens a design file. If a studio jumps straight to concepts without asking those questions, slow down. Don't speed up. The mark is the easy part to picture. The thinking behind it is the part worth paying for.

---

### How much does it actually cost to name a company?
https://kott.studio/journal/cost-to-name-a-company — Aug 2026 — Brand
Answers: how much does it cost to name a company; company naming cost; how naming agencies price a project; trademark screening cost for a business name.

Ask five agencies what it costs to name a company and you'll get five different numbers. One folds it into a five thousand dollar logo package. Another prices it as its own twelve thousand dollar engagement. A specialist shop can run past a hundred thousand for what looks, on paper, like the exact same deliverable: a name, a tagline option, a green light to file. The spread is real. It comes down to one thing: how much trademark and legal defense work actually sits inside that number.

Most branding agencies bill naming at whatever rate they bill everything else, roughly one hundred to one hundred fifty dollars an hour in the US. Fold in a logo, a starter style guide, and the whole project usually lands between ten and fifty thousand dollars, with naming as one line inside that number rather than its own deep engagement. You get a handful of workshops and a shortlist fast. What you don't get, most of the time, is a serious trademark search on every candidate. Just a quick database check to rule out the obvious clashes.

Naming only shops price differently, because naming is the entire business, not a line item. Minimums start around ten to twenty five thousand dollars. Hourly rates run two to three hundred. And a real share of their finished projects land between fifty and two hundred thousand. That money buys several rounds of a hundred or more candidate names, a proper trademark and linguistic conflict check on the shortlist, and someone in the room who can defend that shortlist to a skeptical founder or board. The brainstorm is the cheap part. Screening and defense is the premium.

The government's own cut is small. A standard US trademark application costs three hundred fifty dollars per class online, plus another hundred if the filing is missing required details. That's not where the money goes. The expensive part happens before anyone files: a search across federal and state trademark databases, plus real use on the ground, because a name can be blocked by a mark that was never even registered. Skip that step and you risk a rejected application, an opposition after launch, or a lawsuit once the name is already on the building. Geography moves the number too. The same scope runs twenty five to fifty dollars an hour in lower cost markets, and one hundred to one hundred fifty here. That alone can triple a quote before anyone has written a single candidate name.

When a quote comes in, ask one direct question: is trademark screening included, or is it a surprise add on once you've already fallen for a name? A price that looks too good almost always means that piece got cut. Weighing a generalist agency against a specialist naming shop? Bring your shortlist and that exact question to the first conversation. It costs nothing but the meeting, and it's the fastest way to find out which kind of engagement the name actually needs.

---

### What's actually included in a branding package
https://kott.studio/journal/whats-in-a-branding-package — Aug 2026 — Brand
Answers: what's included in a branding package; branding package deliverables; brand identity system; cheap branding package.

Ask two people for a branding package quote and you can end up comparing a $300 job to a $12,000 one with no way to tell what the extra $11,700 buys. Here's the honest answer. The cheap package gets you a logo file. The real one gets you a system, built by someone who worked out who the brand is for and what it needs to say before opening a design tool. That gap doesn't show up on the invoice. It shows up eighteen months later, when the business has outgrown one PNG file and nobody knows what to do next.

The cheap package hands over surprisingly little. One logo concept, maybe two, exported as a PNG or JPG and occasionally a vector file if you ask nicely. A colour palette worth the name is rare. Typography guidance rarely goes beyond whatever font the logo happens to use, and there's little room to ask for changes once the file lands. This tier runs from a hundred dollars to a couple of thousand, priced like a product on a shelf rather than work done for a specific business. Nobody researched a competitor. Nobody asked what a client should feel looking at the mark.

Here's the piece missing from that tier: brand strategy, and it happens before any design work starts. A studio worth hiring spends real time on positioning, who the brand is competing against, what a client should conclude in the first three seconds, what the business is actually trying to be known for. That conversation can't be templated into a marketplace listing. It needs a back and forth with the people who run the business, not a form with a dropdown menu. Skip it, and the logo that follows is decoration with no argument behind it.

A full identity system looks different on paper. Instead of one file, there's a primary mark, an alternate lockup for tight spaces, an icon that works on its own. A colour palette with actual usage rules. Typography chosen and paired on purpose. And a guidelines document that tells a printer, a new hire, or a freelancer exactly how to use all of it without emailing to ask. That guidelines document is the part a cheap package never produces, because writing rules for work that hasn't been designed yet takes real time. Time is what separates a hundred dollar job from a five figure one.

The gap shows up later, not on day one. A system holds together across business cards, email templates, a pitch deck, packaging, a website, three years of social posts nobody has designed yet. A single logo file doesn't. Someone ends up guessing at the exact shade of blue by month three, stretching the mark to fit a banner it was never built for. Hourly rates for strategy and design work cluster in a similar range, roughly a hundred to a hundred and fifty dollars an hour, whether the studio is charging three hundred dollars or thirty thousand. The price difference isn't a markup on the same hour. It's how many of those hours the project actually contains.

So the useful question for anyone comparing quotes isn't the total number. It's what's inside it. Ask whether strategy work is included before any logo concepts, how many concepts and revision rounds are on the table, whether a guidelines document ships at the end. If the honest answer is that the business needs a system that survives five years of new materials and new hires, that's a conversation for a studio, not a marketplace form. A cheap package can still be the right call for a very small, very early business. It just isn't the same purchase as the one with a guidelines document attached.

---

### Is it your copy or your design that is killing conversions
https://kott.studio/journal/copy-or-design-killing-conversions — Aug 2026 — Conversion
Answers: is my website copy or design the problem; does my website need better copy or a redesign; copy vs design conversion; website gets traffic but no sales.

Clients ask it exactly the way it sounds: is it my copy or my design that's killing conversions. Fair question. Wrong shape, almost always. The two rarely fail alone. A landing page can read beautifully and still lose people at the form. It can look immaculate and still lose people at the first sentence. The real question isn't which discipline to blame. It's where in the funnel people are actually leaving, and whether that leak looks verbal or structural. Answer that first. Then you know which one to fix.

A copy problem has a specific pattern. People arrive, read, spend real time on the page, then bounce right at the call to action. Or they convert, then complain, or churn fast. Nielsen Norman Group's research on interface language makes the point plainly: wording is never neutral. Loss aversion phrasing. A countdown that manufactures urgency. A cost reframed as a favour. Copy that promises one thing while the click does another. All of it chips at trust at the exact moment someone is deciding, and none of it shows up in a screenshot. The page can look flawless and still read as untrustworthy. The ugly part: manipulative copy sometimes lifts the short term number while quietly costing the return visit.

A design problem has its own signature: rage clicks, abandoned forms, a mobile drop off that no amount of rewriting ever moves. Baymard Institute's usability testing puts real numbers on it. Eighteen percent of shoppers abandon a purchase because checkout runs too long or too complicated. The average form asks for close to twelve fields when about eight would do. Only a quarter of sites mark which fields are required and which aren't, so people guess and trip the validation. None of that is a writing problem. Hand the page to the best copywriter in the country and the form still asks for too much, in the wrong order, with no way to tell what's optional.

Here's a number worth sitting with. Nielsen Norman Group documented a case where removing one unnecessary field from a registration form was worth roughly twenty thousand dollars a year in recovered signups. No copy touched. Just one field, gone. Pair that with a Baymard finding: return policy information usually lives in the footer, even though people look for it on the product page itself. Now you can see the two problems compounding on the same page. A clean form asking the right questions, with the one sentence that would have closed the sale, buried three scrolls away. The honest framing is the one the wider conversion research field already uses: test both under one process, and let the funnel data decide which lever to pull first, not a preference for writing or for layout.

A copywriter reads the words. A designer reads the layout. Neither sits at the point where the two interact, and that's exactly where a conversion leak usually lives. It's the practical case for a studio that does both under one roof: not because either skill is weak alone, but because a single-discipline freelancer structurally can't see the seam where the leak actually is. If you're staring at a page that isn't converting, don't start by picking a side. Find the exact step in the funnel where people actually leave, and look at what's happening there, copy and design together, before deciding what to fix.

---

### What an internal tool actually costs, and when it pays for itself
https://kott.studio/journal/internal-tool-cost — Aug 2026 — Product
Answers: how much does it cost to build an internal tool; internal tool development cost; internal tool roi; when does a custom tool pay for itself.

Most quotes for a small business internal tool land somewhere between ten thousand dollars and well over a hundred thousand, for what sounds like the exact same request. That spread isn't a sign someone's trying to take you for a ride. Two things explain almost all of it: where the developer sits, and how tightly the job was scoped before anyone wrote a number down. The part people actually want answered, whether the thing pays for itself, has an honest answer too, and it has nothing to do with revenue.

Look at the rate bands and the gap stops looking mysterious. Development shops charge anywhere from twenty four to forty nine dollars an hour offshore, and fifty to a hundred and forty nine dollars an hour for a team based in the US, Canada or Australia. Reviewed projects on Clutch, the industry's own pricing tracker, run ten to forty nine thousand dollars. The platform's own average project comes in near a hundred and thirty two thousand dollars, over about thirteen months. Put the same feature list in front of a twenty four dollar an hour team and a hundred and twenty five dollar an hour team and you already have most of the gap, before scope even enters the conversation.

Scope decides the final number, not the hourly rate. The pattern behind decades of custom software projects that blew their budgets is consistent: underestimated complexity, requirements that kept changing mid build, users nobody planned for. Queensland's public health payroll system is the extreme case, landing near two hundred times its original estimate, from six million dollars to one point two billion. Almost none of these failed because the developers couldn't code; they failed because nobody locked the requirements before work started. The same mechanism plays out at your scale, just with fewer zeros. "Track inventory" sounds simple until it needs permissions, an audit trail, and an edge case nobody wrote down, and the quote keeps climbing for the same reason a public agency's did, not because anyone lowballed you to get the job. The scoping work a studio does before a line of code gets written is what catches that early, not a cheaper rate.

Return on investment is the wrong question for an internal tool, and most of what gets published about it dodges that honestly. An internal tool has no revenue line, so there's no clean calculation to run. The real payback shows up somewhere else: hours a person no longer spends on a manual task, an error rate that drops, a subscription you stop paying every month. Anyone selling you a tidy ROI percentage for a piece of internal software invented the number.

Here's what that looks like when it actually works. Someone who built an internal password manager for their company described it afterward on a public forum: the build took four to six person months of developer time. A commercial equivalent licensed for five thousand seats would have cost more in a year than that one time build did, in salary alone. No revenue entered the calculation anywhere, and it still paid for itself within twelve months. The rule holds past that one example: build when the workflow has rules or handoffs no off the shelf tool covers, buy when the problem looks exactly like everyone else's.

None of this gets settled by comparing a single quote against your gut feeling about what it should cost. Write the scope down first, in enough detail that whoever prices it also has to live with what they built two years from now. Then compare quotes against that document, not against each other.

---

### Is a branding agency worth it when you are still small?
https://kott.studio/journal/is-a-branding-agency-worth-it — Aug 2026 — Brand
Answers: is a branding agency worth it; branding agency vs freelancer; when to hire a branding agency; branding agency cost for small business.

Yes. Once you have outgrown a logo and a font pairing, and your brand needs to hold up across more channels than one person can patch by hand. Before that point, an agency is money spent on reassurance, not results. The real test was never the price tag. It is whether you have actually hit the ceiling where a freelancer, or a DIY kit, stops being enough.

The price gap between the three options is bigger than most owners expect. A DIY kit runs 50 to 200 dollars and costs you time instead of money. A freelance branding expert typically runs 300 to 1,500 dollars for comparable visual work, because one person with lower overhead moves faster on a smaller job. An agency starts around 3,000 dollars and climbs from there, billed by the hour and scaled to how many deliverables and revision rounds the project needs. That gap is not padding. It is the size of the team, and the coordinated thinking, behind the file you eventually get back.

Most full branding projects on Clutch land between 10,000 and 49,999 dollars. The average full engagement runs about 71,652 dollars across roughly eight months, close to 8,868 dollars a month. Hourly rates for strategy, messaging, and naming work cluster around 100 to 149 dollars an hour in North America. Numbers like that rule an agency out for plenty of small businesses. That is fine. It usually means you are not the buyer yet, not that agencies overcharge. What that budget buys is not more hours at the same job a freelancer already does. It buys a team running strategy and execution together, instead of one person doing both in sequence, alone, on their own calendar.

You know you have outgrown the freelancer stage when three things start happening at once. The identity keeps needing a patch, a sales deck here, a second product line there, a new channel, and someone, usually you, patches it together by hand because there is no system behind it. Conversations with customers or investors start turning on positioning and price, not just whether the product works. That shift means the brand is doing commercial work now, not decoration. And the freelancer relationship hits its own ceiling: every new request becomes its own small project, there is no strategy layer behind the files, and one person's calendar is now the bottleneck on your growth.

What actually changes at the agency tier is the definition of the job itself. Brand management means controlling how a business is perceived across everything a customer touches, not just the logo: pricing, packaging, the experience of dealing with you, the story that gets repeated when nobody in the room works for you. Accounting standards recognize brand value as a real, quantifiable asset, for exactly this reason. In a market where the product alone rarely wins anymore, the brand is the more durable thing holding the price up. A freelancer relationship cannot structurally include that strategic layer. It is the actual thing you are paying an agency for.

Before you call anyone, run the test yourself. Count how many places your current identity needs a manual patch this quarter: a deck, a landing page, a new hire's onboarding, a new product line. If that number keeps climbing, and pricing conversations already mention the brand without you bringing it up, you are past the point where a freelancer's calendar can keep up. That is when a real conversation with a studio is worth having.

---

### Do testimonials actually increase conversions?
https://kott.studio/journal/do-testimonials-increase-conversions — Aug 2026 — Conversion
Answers: do testimonials increase conversions; testimonial placement conversion rate; specific testimonials vs generic reviews; how to write a testimonial that converts.

Testimonials increase conversions, on average. But that number hides more than it tells you. VWO has run test after test on the same underlying move: add a testimonial, or move one. The results range from a 6.74 percent lift in purchases, to a 52 percent jump in demo requests, to a 64.53 percent gain from moving one quote above the fold. That's too wide a spread for testimonials work to mean much on its own. What separates the small lift from the large one isn't whether you have a testimonial. It's where you put it, what it says, and whether the reader believes you didn't write it yourself.

Position changes the outcome on its own, before you even look at the words. Move a testimonial above the fold and conversions can rise 64.53 percent, as one landing page test found. Underwater Audio repositioned a single testimonial so it landed in the reader's natural eye path, right before the buy button. Nothing else on the page changed. Sales rose 35.6 percent. Most small business sites do the opposite: testimonials sit in a footer strip, or on a dedicated reviews page nobody visits on the way to checkout. That's exactly the placement the winning tests moved away from. Treat placement as a design decision, made against one specific moment of hesitation on one specific page, not a block you paste in at launch and forget.

Specific beats generic, every time this gets tested. A precise number reads as more credible than a round one: most people assume a round figure got rounded up to look better, so 60.37 percent earns more trust than a plain 60. A testimonial that names a real problem, and how it got fixed, will beat one that just says nice things. A single specific testimonial has even outperformed a large but vague number with no story behind it, like a subscriber count. "Great to work with" answers nothing a hesitant visitor is actually asking. "Our checkout abandonment dropped after the flow got rebuilt" answers the exact question already in their head.

Who's telling you matters as much as what they say. Visitors quietly discount a testimonial they know the brand chose and published itself, on the assumption the bad ones got cut. In usability research on direct-to-consumer sites, most buyers went looking for outside verification before they trusted an on-site claim at all. The on-page reviews barely got a second look. Proof visibly outside the brand's control does better: one company added a widget from an outside review platform, changed nothing else, and saw a 58.29 percent lift. A quote you can't fully control is worth more than one you wrote yourself, even when both say the same thing.

Curation matters more than volume. A thin, unconvincing number attached to a testimonial section can read as proof the thing isn't popular, which lands worse than showing no number at all. Five interchangeable one-line quotes stacked in a slider don't read as five reasons to trust you. They read as a slider. Most people scroll straight past sliders.

None of this is a plugin. It takes finding one real client willing to talk. Asking the question that gets the specific detail instead of the polite compliment. Editing that down to the one objection it needs to answer, then deciding exactly where on the page a reader is hesitating enough to need it. That's real work, not a settings toggle, which is exactly why most sites skip it and end up with a slider instead. If you want it built properly rather than pasted in, that's what we do.

---

### Your conversion rate dropped after the redesign, here is why
https://kott.studio/journal/conversion-rate-dropped-after-redesign — Aug 2026 — Conversion
Answers: conversion rate dropped after website redesign; why did my conversion rate drop after redesign; website redesign lost conversions; tracking broke after website redesign.

Your conversion rate dropped after the website redesign. That is almost never people rejecting the new look. It is one or two specific things that changed underneath the design, and both are usually findable within a week if you know where to check. The first bucket is something a visitor can no longer find or do on the new site. The second is something the team can no longer measure correctly.

One documented case removed roughly 15 percent of a site's pages during a redesign and watched organic traffic fall by close to half. A hit wildly out of proportion to the size of the change. That is the pattern worth sitting with. A redesign gets judged in a review meeting on how clean it looks, not on whether the path a paying visitor takes still works the way it used to.

Start with tracking. It is the fastest thing to rule out and the easiest for a team to skip. Analytics and conversion goals rarely survive a rebuild untouched. A tag fires on the old button and not the new one. A thank you page URL changes and the goal quietly stops counting. A form ID gets regenerated and the event never sends. Some of the drop you are looking at is not a real change in visitor behaviour, it is a measurement gap, and it is worth ruling out before anyone touches a single pixel of the design.

If tracking checks out clean, look at what got buried. Pricing. A phone number. The one call to action that used to sit above the fold, now gone or three clicks deeper because the new layout wanted to look calmer. The redesign usually looks better in the room. It removed friction the team wanted gone, and along with it, the piece of information a buyer still needed before saying yes.

The next problem is scope. Change the layout, the copy, the tracking and the page structure in a single release and you lose the ability to tell which one cost you the conversions. A studio doing this properly stages the rollout, or at minimum keeps a change log tied to the launch date, so a drop can be traced to a cause instead of a guess made a month later.

The most preventable cause on this list is shipping the pages that make money untested. Checkout and form friction alone accounts for a meaningful share of abandoned orders across the industry, and the average checkout still carries more fields than it needs. Skipping usability testing on the exact flow that makes money is choosing not to find these problems before launch. You find them afterward instead, at the client's expense.

The conversion number itself will not tell you which of these happened. It only tells you that something did. Compare the new page against the old page's actual recorded behaviour on the same step, not against how the new one performs in the abstract. Watch a handful of session recordings on the exact point where the funnel now leaks. Do not start with the whole site.

This is the part of the job that happens before launch, not after the number falls: testing the pages that make money against the old baseline while there is still time to fix what breaks. If your last redesign shipped without that step, that is the thing to change before the next one. Not the colour palette.

---

### What a marketing retainer actually costs, and what it buys
https://kott.studio/journal/marketing-retainer-cost — Aug 2026 — Marketing
Answers: marketing agency retainer cost; how much does a marketing retainer cost; monthly marketing retainer pricing; what does a marketing retainer include.

A marketing retainer usually runs one to ten thousand dollars a month. Most agencies sit inside that band, no matter what the pitch deck implies. The twenty five thousand dollar figure people brace for before their first call is real, but it belongs to roughly one agency in ten, mostly firms serving North America and Europe. If a retainer conversation opens on a much bigger number with no explanation attached, that is the first thing to question, not accept.

Inside that range, the shape holds fairly steady. About half of agencies average one to five thousand a month, which usually buys a narrow scope: one channel done properly, not a full marketing function. Roughly a third sit between five and ten thousand, where account management and a wider mix of channels start showing up. The rare large retainer, twenty five thousand and up, buys a dedicated team working your account. Not one person working harder for the same money.

Why two quotes for work that sounds identical can land so far apart usually comes down to what is hidden underneath the monthly number. Agencies price general marketing work far more cheaply than specialised work. Strategy, paid media, and content each carry their own rate, so a retainer that looks expensive is often just buying more of the specialised kind. A quote that will not say which hours it is charging for is the one to distrust, not the cheaper one.

Agencies and consultants also charge roughly two and a half times what a solo freelancer charges for work that sounds identical on paper. That gap is not effort. It is structure. Someone covering your account when the person you hired is out. A second pair of eyes on the numbers. Reporting that happens whether or not you ask for it. A freelancer can do excellent work for less, but cannot offer a backup bench by design, and that is worth saying plainly before you compare two quotes on price alone.

Experience gets priced in too. An agency a couple of years old typically charges about a third more than one just starting out. A decade in, that same firm can charge more than double what a newcomer asks for a scope that reads identically on a proposal. That premium buys judgment you cannot see on a pitch deck, the client problems already solved once, the mistakes it will not relearn on your account.

It helps to stop treating a retainer as a monthly bill and start treating it as time you are buying inside a relationship. Agencies are keeping clients longer than they used to. Three year plus engagements are becoming the norm, not the exception. A retainer earns its renewal by getting properly embedded in how a business runs, not by staying the cheapest line on a spreadsheet. That is the honest measure of whether one is working.

Before you put two retainer numbers side by side, ask four questions. Which channels are actually covered. Who on the team is assigned to your account. How often you get reporting. What the minimum term is. Answer those and two retainers priced identically can turn out to be entirely different jobs, and a studio that hesitates on any of them is telling you something about the number too.

The number on a retainer quote is the least useful part of it. Ask what it buys, channel by channel, person by person, before deciding whether it is worth it. A studio that answers plainly is the one worth taking seriously.

---

### What counts as a good conversion rate for your site
https://kott.studio/journal/good-conversion-rate-for-your-site — Aug 2026 — Conversion
Answers: what is a good conversion rate for a website; good conversion rate benchmark; average website conversion rate; landing page conversion rate.

There is no single good conversion rate. The phrase hides three different measurements wearing the same name: how many site visits end in a purchase, how many landing page visits end in an opt in, and how many ad clicks end in a tracked action. This quarter, ecommerce sites averaged 1.4 percent site to purchase. Landing pages averaged 6.6 percent visit to opt in. Both numbers are true. Neither tells you anything about the other.

The reason both can be true comes down to the denominator, the number you're dividing by. A site to purchase rate divides by every visitor who ever landed on the site, most of whom were never going to buy anything today. A landing page rate divides by a narrower, more qualified group: people who already clicked an ad or a link built around one offer. Google Ads goes narrower still. It defines conversion rate against ad interactions, not site visits at all, so a client quoting 5 percent from their ads dashboard isn't describing the same thing as a 5 percent site wide rate. Most conversion rate anxiety comes down to comparing two figures that were never measuring the same funnel.

The published ranges bear this out. Landing page conversion runs from 3.8 percent for SaaS to 12.3 percent for events and entertainment, most industries falling somewhere between. Ecommerce sectors cluster far lower, close to 1.4 to 2.4 percent, because that number has to survive the whole path from browsing to paying. Traffic source moves the figure on its own. Email traffic on the same page converts several times higher than paid search or display, with nothing on the page itself touched. Price, how complex the sale is, and how much trust a visitor needs before acting: all of it shifts the number before design even enters the conversation.

The only conversion rate worth chasing is your own: measured against your own history, on the same definition, over time. A rate that drops below your baseline is diagnosing something, not decorating a report. Sometimes it's a traffic mix that changed. Sometimes a campaign pulled in the wrong audience, or a funnel stage got redefined without anyone noticing. A marketer can check all three alone, no design work required. What's harder to see from inside the business is whether the page still matches the person arriving on it, once those easier explanations are ruled out. That's usually where a studio earns its fee, not a redesign nobody asked for.

So before touching the design, know which number you're actually holding: site wide, landing page, or ad platform. They aren't interchangeable. Compare it against your own history, not an industry chart built from someone else's traffic and someone else's price point. If the honest read is still confusing after that, it's worth a second pair of eyes before a rebuild.

---

### Does site speed really move your conversion rate
https://kott.studio/journal/site-speed-and-conversion-rate — Aug 2026 — Conversion
Answers: does website speed affect conversion rate; site speed and conversion rate; page load time and conversion; slow website losing customers.

Yes, and the honest range is bigger than most people expect. The BBC lost about 10% of users for every extra second a page took to load. Google's own research shows a half second delay on mobile measurably drops conversion too. That doesn't mean shaving 200 milliseconds off your homepage will move revenue this quarter, though. Most of what clients call a "speed problem" is something else wearing a stopwatch.

There's a real mechanism behind the numbers, not a marketing line. Nielsen Norman Group's research on load time found that a delay of around one second is enough to interrupt a person's conscious train of thought. Call it a small system check rather than impatience: something feels broken, and the visitor starts looking for a way out before they've consciously decided to leave. That's the moment you're actually losing, not the page weight itself.

The data trail behind these claims is older and more specific than the plugin vendors let on. Google and Bing found half second delays cutting conversions back in 2009. Mozilla cut load time by two seconds in 2010 and saw a 15% lift. By 2016, more than half of mobile sessions were abandoning a page once it passed three seconds. Real, dated, named studies, not a universal law you can apply to any site at any traffic level. Treat a stat with no source attached the way you'd treat a client testimonial with no name on it.

Here's where the plugin fix runs out of road. Speed gets decided at build time: the framework, the image pipeline, what has to load before the page is even usable. A caching plugin bolted onto an existing site buys you a little, sure, but it can't undo a decision made months earlier when someone chose the stack or shipped every image at full resolution. That's a build decision, made once, by whoever built the thing. Fixing it after launch with a settings panel is treating a structural problem like a stain.

The studies also don't cleanly separate speed from everything else that's broken. Baymard's checkout research finds that "the site had errors or crashed" accounts for about as many abandoned carts as delivery being too slow, and a complicated checkout flow sits right beside both. The average US checkout still asks for more than twenty fields when twelve or so would do. A technically fast page that throws an error, or interrogates the visitor for their life story, loses the sale for reasons no speed score will ever flag.

So before you spend a budget chasing a page speed score, watch where people actually drop off. Run a real test, sure, but look at the step in your funnel where visitors leave too, and ask honestly whether it's load time or friction doing the damage. If it turns out to be the build itself, that's a conversation worth having with whoever built it, not another plugin to install.

---

### What belongs in a website brief before you talk to a studio
https://kott.studio/journal/website-brief-before-hiring-studio — Aug 2026 — Websites
Answers: what to include in a website brief; website brief before hiring a studio; budget range for a website project; website brief checklist.

Search a website brief and you get a stack of downloadable templates: sections for goals, audience, deliverables, timeline. None of them say which section actually changes what a studio quotes you. Two things do. A real budget range, and a named decision maker. Everything else on the template is scaffolding around those two.

Start with one sentence: what the site has to do, not what it should look like. Is it there to convert visitors into calls? To sell directly? To hold a brand together across a dozen landing pages, or just stop looking amateur next to a competitor's site? Name who reads it too, and what they already believe walking in. A studio scoping "a marketing site" with no stated job to do will quote the wrong project, then charge you again later to fix the scope.

Give a range, not a number you've researched to the dollar. Custom studio work in the US typically runs $100 to $149 an hour, and full projects land anywhere from under $10,000 for something simple to $100,000 or more once ecommerce, a content system, or custom copywriting enters the brief. That spread isn't a failure of research on your part. It's the actual shape of the market. What the range buys you is a studio that can tell you honestly, on the first call, whether you're a fit, instead of three weeks into a proposal neither of you should have started.

Name who signs off, and how. One owner deciding alone moves differently than a marketing lead who has to bring it to a board. This is the section most templates skip entirely, and it's the one that tells a studio who they're allowed to email with a question, and who gets to change the brief midway through. A brief with no named approver is how a site gets rebuilt in week six by someone who was never on the first call.

List the pages and the must-have features. Just as usefully, say what isn't in this round. A booking system, a blog, a members area: any of these changes both the price and the calendar, so say plainly if it's coming now or later. Leaving it vague doesn't keep options open. It just moves the disagreement to the invoice.

State the real date something needs to be live, and why: a launch, a trade show, a funding close, a lease running out on the old site. If there's no real deadline, say that too. A soft "as soon as possible" reads to a studio as no deadline at all, and gets scheduled behind the client who gave them a true one.

None of this needs to be long. A page, honestly filled in, tells a studio more than a stack of mood boards ever will. Expect a good studio to push back on parts of it once the work gets real. That's the brief doing its job, not a sign it was wrong. Bring the objective, the range, the decision maker, the scope, and the date to the first call, and the conversation starts where it should: on the work, not on guessing what you meant.

---

### Web design retainer or project fee: which one you actually need
https://kott.studio/journal/web-design-retainer-or-project — Aug 2026 — Websites
Answers: web design retainer vs project; web design retainer or project fee; should i hire a studio on retainer; one time website project cost.

Everything written about retainers and project fees is written for the studio pricing itself, not for you deciding what to buy. Here's the answer, plain: it isn't about which one costs less. It's about whether the work has an end date. A website redesign, a new landing page, a rebrand: that's a project. Design work that has to keep moving month after month: that's a retainer. Get the category wrong and you'll overpay for structure you don't need, or underbuy and end up re-briefing a new studio every few months.

A project fee buys a fixed scope, a fixed price, a fixed date, all agreed before the first invoice goes out. It fits work with a real edge: a redesign, one landing page, a brand system, an MVP screen set to show investors. The studio absorbs the risk of a job that turns out bigger than it looked on paper. You absorb the cost of anything outside what was agreed, and that's a change order, not a favor. A scope written down honestly matters more than the number at the bottom of it. Industry ranges for a single project run roughly three to fifteen thousand dollars depending on size and studio. That range tells you more about scope than it does about quality.

A retainer is different: a standing monthly agreement for a cadence of work, not one delivery. It earns its cost when there's genuinely more than two or three weeks of design work queued at any given time, when a product or brand is still changing shape, or when several smaller pieces, a landing page here, an ad set there, a deck next month, need to look like they came from one hand. The upside is real. A predictable monthly number. A studio that stops relearning your brand from zero every time you call. The downside is just as real: a slow month still gets billed, and a busy one might mean waiting your turn behind someone else's retainer. Ongoing retainers tend to run somewhere from one to five thousand a month, scaled to the actual cadence of work rather than a flat rate everyone pays.

Here's the part nobody says out loud. Hopping between one-off projects has a hidden cost of its own. Every new studio starts from zero: re-explaining the brand, re-sending the same brief, paying again for groundwork the last studio already did once. Past two or three separate projects a year, that ramp-up tax usually adds up to more than a retainer would have cost outright. That's not a reason to default to a retainer. It's a reason to actually add up what the year looks like before assuming the project route is cheaper.

If this is your first real website or your first brand system, buy the project. You want one thing finished, on a date, at a price you agreed to in writing, and you don't yet know what ongoing work would even look like. A retainer only earns its keep once you've shipped that first big thing and the requests keep coming anyway: another page, another campaign, another round of assets that need to match what came before.

Whichever you choose, get three things in writing before you sign anything: what's included, how many rounds of revisions come with it (two or three is normal), and what costs extra. That single page will save you more arguments than any pricing model will. Not sure which side of that line your work sits on? That's a five-minute conversation, not a guess you make alone from a pricing page.

---

### What website maintenance really costs when a studio does it
https://kott.studio/journal/website-maintenance-cost-per-month — Aug 2026 — Websites
Answers: website maintenance cost per month; how much does website maintenance cost; website maintenance retainer cost.

Website maintenance costs anywhere from ten dollars a month to more than seven thousand. That is not a typo, it is the whole problem. Published pricing guides put a full monthly retainer at roughly $7,100 on average, while a bare WordPress plugin update plan runs $10 a month, and hosting itself sits underneath both of those at $75 to $200 a year, with a domain adding another $15 to $25. Nobody quoting maintenance is lying. They are describing two different jobs and calling both of them by the same word: keeping a site alive, and actually changing it.

The cheap end, ten to roughly two hundred and twenty five dollars a month, buys exactly what it sounds like. WordPress core and plugin updates, a security scan, uptime monitoring, someone remediating whatever the scan turns up. It is a subscription, not a relationship. If your site is finished and nobody is asking for changes to it, this tier is honestly enough, and paying more for it just buys a nicer logo on the invoice. The trouble starts when a client on this plan expects retainer speed: same day copy edits, a new section before Friday. None of that ships at this price.

The expensive end is not pricing maintenance at all. A $7,100 a month retainer is pricing unlimited small tasks, content swaps, new sections, a person who picks up when something breaks or the founder wants something moved. Closer to hiring a part timer than buying a plan. That is why stacking it against the ten dollar option is like comparing a gym membership to a personal trainer: same category, nothing alike. It only earns its price if the client generates enough real requests to use it. A brand new one page site on this retainer is paying for capacity nobody touches.

Hosting already prices this same split, one layer down. Shared hosting runs two to fifteen dollars a month. Managed hosting, where the provider takes over server admin and patching, runs fifteen to fifty dollars or more. Nothing about the server changed. What changed is who does the work of keeping it current, and that is exactly the premium a studio retainer charges for at the site level. Not the site staying online. A person keeping it patched, secure, and current without being asked.

There is a simple test before signing anything: read the line items. If the quote only lists updates and security, you are buying the cheap tier, and it should be priced like a utility bill. If it lists content changes, dedicated hours, or a turnaround promise, you are buying the expensive tier, and it should be priced like staffing. Neither is a bad deal at its own price. The only real mistake is paying retainer money for subscription work, or expecting subscription speed at a subscription price.

Before renewing anything, pull last quarter's maintenance requests and sort them: what kept the site alive, and what actually changed it. Most founders have never made that split, and most are surprised by which pile is bigger. A studio worth hiring will tell you honestly which tier your site needs, rather than sell you whichever one happens to be on the price sheet. That is the difference between a vendor and a studio. Worth finding out before the next invoice, not after.

---

### How long a website actually takes to build, phase by phase
https://kott.studio/journal/how-long-a-website-takes — Aug 2026 — Websites
Answers: how long does it take to build a website; website build timeline; how long does a website take; custom website timeline.

How long does it take to build a website? Ask a builder and the answer is a few days. Ask a studio and it's six weeks. Both are telling the truth about different jobs. A standard custom build runs two to six weeks from kickoff to launch; the full range across real projects spans roughly four weeks to a year, depending on scope. The builder skipped straight to the part anyone can do alone. The studio is quoting everything else: the parts most people forget exist until they hit them.

Planning comes first, and it eats more calendar time than it looks like it should. This is where scope gets fixed: what the site needs to do, who it needs to convince, what content already exists, and what has to be written from scratch. A studio walks a client through this before touching a single pixel, because every hour spent here saves three later. Most clients treat planning as paperwork. It's actually the only phase where the client, not the studio, controls the pace. A vague brief costs a week before design even opens.

The single biggest cause of a slow build isn't the studio. It's the client's own content. Copy, photos, product details, testimonials: whatever the site needs to say has to exist before a page can be finished, and it's almost always the last thing ready. A builder site that goes live in an afternoon usually means the content was already sitting in a folder, written and approved, before anyone opened the builder. The phase didn't vanish. It happened earlier, off a clock nobody was counting.

Once scope and content are settled, design comes next: wireframes for structure, then the actual visual design, usually with a round or two of revisions before anyone signs off. Development follows, turning an approved design into a working site with real functionality behind it, not a static picture of one. Both phases compress on a simple brochure site and stretch hard on anything with logins, payments, or custom features. This is the part that looks, from the outside, like building the website. It's maybe half the actual timeline.

Then comes testing, the phase a site built alone usually skips entirely. Checking it on different devices. Clicking every link. Timing how fast it loads. Watching someone unfamiliar with it try to use it before it goes live. A site that loads and a site that's been tested aren't the same claim. The gap between them never shows up on launch day. It shows up three months later, in a support inbox full of people who couldn't find the contact page on their phone.

Launch isn't the end of the phase list, whatever the timeline graphics suggest. Every honest version of this process, from an agency's own workflow diagram to the formal development lifecycle taught in computer science courses, treats what comes after launch as its own ongoing phase: fixes, updates, small improvements, security patches. A website nobody touches after the launch party is a website quietly going stale. Budget attention for this too, not just for the build.

The honest answer is a range instead of a single number for one reason more than any other: how fast the client responds. A studio getting same day feedback and finished copy on time can run a project in six weeks flat. The identical project, with a week of silence between every round of feedback, can drift to ten or twelve. Build speed rarely changes. Decision speed does. Once scope and content readiness are actually known, the timeline stops being a guess and becomes a number someone can commit to.

None of this is a reason to dread the process. It's a reason to ask a studio, before signing anything, which phase your specific project is likely to stall in. A studio that's done this enough times can usually tell you in the first conversation: content, decisions, or scope creep, pick one. That answer is worth more than any generic week count, because it's the one thing that actually predicts your timeline instead of describing someone else's.

---

### Design subscription or project quote: what each one actually buys
https://kott.studio/journal/design-subscription-vs-project-quote — Aug 2026 — Studio
Answers: design subscription vs project quote; design retainer vs project pricing; when to choose a design subscription; design subscription or one time project.

A design subscription buys you capacity. A set amount of design time each month, on tap, for as long as you keep paying. A project quote buys you a result: a fixed price for a defined piece of work, with a start and a finish. Both are honest pricing models. The mistake is picking one because it's the one you were offered, not because it matches how much design work your business actually has coming. A studio quoting you a monthly retainer when you have one deliverable and no ongoing need is selling you a commitment you don't need. Flip it around: quote you a fixed project when your design needs never actually stop, and you'll be rebuying the same relationship every few months.

A subscription, sometimes called a retainer, is a recurring monthly fee for ongoing capacity: a queue you can drop requests into, priority turnaround ahead of one off clients, and a team that keeps learning your brand and your product instead of relearning it every engagement. Ranges run wide by scale. Small businesses typically pay somewhere from one thousand to five thousand dollars a month. Mid market companies pay five thousand to fifteen thousand. Larger companies go well beyond that. The model earns its keep when there is always two or three weeks of real work queued: a product roadmap that keeps shipping screens, a marketing team that needs assets every week, a brand still being built out piece by piece.

A project quote is the opposite shape. One fixed price for one defined scope, a start date and an end date, no ongoing bill once it ships. It fits a rebrand, a website, a launch campaign, anything with a real definition of done. The honest range spans from a few thousand dollars for something small to well over a hundred thousand for a large, complex build, with the average project landing somewhere in the tens of thousands. The catch is scope. About half of fixed price design projects run over their original scope, by roughly a quarter on average, whenever the brief wasn't locked down before work started.

Neither model is free of a catch the sales conversation tends to skip. A subscription can quietly turn into a dependency. Cancel it and you may lose not just future work but support on what was already built, since some studios tie post project help to staying on the plan. Long retainers, in particular, are structured as much for the studio's cash flow as for your actual pace of need, and a client locked into a year long commitment carries that risk regardless of how the work goes. A project quote avoids that trap. You pay once, you own the outcome. Its risk sits earlier, in the brief. Leave the scope vague and one more thing creeps in until the fixed price stops covering the actual work, with the studio deciding what counts as extra.

The decision is simpler than either sales pitch makes it sound. Count the design work you actually have queued right now, not the work you hope to need eventually. Continuous and overlapping work, a product that keeps shipping, a marketing calendar that never empties, an in house team that needs to move faster than it can hire, points to a subscription. One deliverable with a real finish line, a new site, a rebrand, a launch, points to a fixed quote, and paying for ongoing capacity you won't use is just cost with no upside. A studio worth hiring will ask what your actual cadence looks like before it recommends either one.

Before signing anything, answer that cadence question yourself first. Write down what design work is actually queued for the next two months, not the wish list. Bring that list to the first conversation with a studio, not a preference for one pricing model over the other. And treat a studio that pushes the same model on every client, regardless of what that list says, as a signal to keep asking questions before you sign.

---

### How to choose a web design studio without getting burned
https://kott.studio/journal/choosing-a-web-design-studio — Aug 2026 — Studio
Answers: how to choose a web design agency; web design studio red flags; who owns the code after a website project; website hosting after the agency is gone.

Before you hire a studio to build your website, skip the portfolio. Check who owns the code, who hosts it, and who's still answering the phone six months after launch. Most people vet the fun part first: the visuals, the case studies, the pitch. It's the boring part where people get burned, usually in a contract clause nobody read closely, or a hosting arrangement nobody thought to ask about. Choosing a web design agency for anything beyond a single page starts there.

Ask for full code ownership and repository access at handoff. A studio that hedges is telling you something true about how the relationship will go. Some shops build on a proprietary template or a locked platform on purpose, so leaving later means starting over instead of just switching hosts. Ask directly: at handoff, do you own a repository you can move anywhere, or are you renting a system only this studio can touch. A studio confident in its own work hands over the keys without flinching. One that stalls, changes the subject, or quotes an extra fee just to export your own site has already answered you. This isn't a clause to negotiate later. It's the difference between owning a website and leasing one from a landlord who can raise the rent whenever they like.

Hosting is where a lot of studios get vague, often on purpose. Many resell shared or VPS hosting under their own brand, so you never learn who the real underlying host is, or what your account even looks like from the outside. Ask plainly: where does this site live, under whose account, and what happens to it the day the contract ends. A studio that answers in one sentence, with a name you can look up, is being straight with you. One that talks around it, or implies you wouldn't understand the details anyway, is setting up a situation where leaving them costs you your site's uptime along with the relationship.

If a proposal never mentions security, backups, or what happens after launch, that's not an oversight. It usually means the studio's job ends the moment the site ships. Everything that breaks afterward becomes your problem, solved alone or paid to someone else to fix. A studio that expects to still be useful in six months offers some version of a maintenance retainer, spelled out in the proposal, not improvised later once something's already broken. You don't have to take the retainer. You do have to hear it offered.

Watch how a studio behaves before you've signed anything, because that behavior doesn't improve afterward. A team that asks few questions on the first call, promises results it has no way of knowing it can deliver, or can't explain in plain language how it actually works, won't suddenly turn transparent once the invoice is paid. The studios worth hiring push back. They'll tell you when an idea won't work, tie their quote to a written scope instead of a vague estimate, and treat the discovery call like the start of a working relationship, not a sales pitch with a deadline.

Before you sign anything, ask the three questions above out loud: who owns the code, who hosts it, who maintains it once it's live. A studio with nothing to hide answers all three without hesitation. One that dodges even a single one has already told you what working with them will be like. Better to find that out now than six months into a contract.

---

### What a landing page costs, and when one page beats a whole site
https://kott.studio/journal/landing-page-cost — Aug 2026 — Conversion
Answers: how much does a landing page cost; landing page cost; landing page vs full website; single page website cost.

A landing page usually costs less than a full site. The reason is almost boring: less to build, not a different rate card. Charge a studio four figures for a full website and they'll usually land in the same range for one page done properly, just at the low end of it. On the numbers agencies actually report, full custom projects run from roughly $2,000 to $100,000, most under $10,000. A single page sits at the bottom of that band. So the real first question isn't what's cheap. It's whether the job needs one page or several.

So what does that bill actually cover on a single page? One round of copy. One layout. One build. No content management system behind it, no navigation to plan, no sitemap. The bigger swing in price is where the studio sits, not what they're building. Agencies in the US, Canada and Australia typically bill $100 to $149 an hour; teams in Eastern Europe, Latin America and parts of Asia bill $25 to $49 for comparable work. Two quotes for the same page, three or four times apart, and the page itself is rarely why.

Page count is not what pushes a landing page's price up. Custom copywriting does. A form wired into a real CRM, a payment processor or a booking system does. Animation and interaction work does. Tracking set up properly for paid traffic does. A single page carrying all four of those can cost more than a five-page brochure site with none of them. Scope decides the price far more than the page count on the invoice.

There is a real case for one page, and it's narrower than most people assume. A dedicated destination for a paid ad or an email send, built around a single offer. A placeholder before a full site launches, there mainly so Google has already found and indexed the brand. A cheap, fast way to test whether an idea has any demand before committing to a proper build. In each of those, the visitor has already been primed elsewhere. The page's whole job is one action, not a menu of them.

Here is the honest tension. One page cannot split traffic across more than one search intent, so it cannot be found for more than one thing at a time. It will not build the depth of content, or the inbound links, that come from a site people actually reference and quote. That caps organic growth on purpose, and that's fine for a campaign page with a fixed lifespan. It's a real cost if organic search is meant to carry the business over time, not just this quarter.

A single page gets outgrown fast: more than one offer, more than one audience, a real query worth ranking for beyond the one the page was built around, a plan to publish anything over time. At that point the landing page stops being the cheaper option and starts being the thing standing in the way. Better to say so early than let someone spend on a page that needs replacing within six months.

The question worth bringing to a studio, then, isn't how much for a landing page. It's whether a landing page is even the right size for what you're trying to do. That's a conversation, not a quote, and it takes five minutes to have before either one gets written.

---

### Why do web design quotes vary so much
https://kott.studio/journal/why-design-quotes-vary-so-much — Aug 2026 — Studio
Answers: why do web design quotes vary so much; why is one web design quote so much higher than another; how to compare web design quotes; what affects web design pricing.

Two agencies quote the same brief. The numbers land nowhere near each other, and it is rarely because one studio is better than the other. The brief was never actually identical once each agency finished defining it in their own head. Industry pricing surveys put the honest range for a web design project somewhere between $2,000 and $100,000, and hourly rates alone span roughly $25 to $49 on one end and $100 to $149 on the other, depending on who is doing the work and where they are doing it from. That gap is not noise. It is the whole answer, spread across a handful of decisions each agency made before anyone typed a number.

The line item that moves the price most isn't skill. It's how tightly the project got scoped before a figure hit the page. One studio prices exactly what you asked for on the call. Another prices what they expect the project will actually need once the real questions surface: the missing content, the extra revision round, the integration nobody mentioned in the brief. That second number looks worse on a spreadsheet next to the first one. It's often the honest one, and the tighter quote can look like the better deal right up until the change orders start.

A proposal for a fully custom build and a proposal for a heavily customised template can read almost identically on paper: same page count, same feature list, a similar looking mockup. The work behind them isn't the same job. Template and builder based work leans on existing structure, which genuinely cuts hours. Custom design means building layout, imagery, and every interaction from nothing, which doesn't. If a quote looks unusually low, ask which one you are actually being sold. The answer changes what you get on delivery day.

Staffing changes the number too, even inside a single agency. The same brief costs more when it goes to a senior designer than when it goes to someone earlier in their career, and neither choice is wrong on its own. Location stacks on top of that: studios based in North America, Australia, or Western Europe bill meaningfully more per hour than offshore or nearshore teams doing comparable work. The mismatch shows up when a client compares two numbers without knowing who is actually behind either one.

A quote is also not just design hours. Copywriting, SEO setup, revision rounds, and support after launch get folded into some quotes and billed as extras in others. Any functional complexity in the brief, a content system, a database, e commerce, a third party integration, adds real engineering time that a design only quote never had to price in. Two studios can scope that functional layer very differently even when the page counts on both proposals match exactly.

So compare quotes on what is actually in them, not the total at the bottom. Ask what custom means in this specific proposal, who on the team is doing the work, and what happens the week after launch. A studio worth hiring will answer all three without flinching, because a clear answer is what tells you the number in front of you is honest. The cheapest quote that skipped the unknowns is often the expensive one six months in.

---

### What a good studio needs from you to do its best work
https://kott.studio/journal/what-a-studio-needs-from-you — Aug 2026 — Studio
Answers: how to work with a design studio; what to give a design studio; creative brief for a design studio; how to give feedback to a designer.

A studio's work is only as good as what you hand it going in. That's the part clients forget. When a project drags or the result comes back generic, the instinct is to blame the studio's process. Usually it isn't that. It's a brief that says "make it feel premium," no one person who can actually sign off, feedback that trickles in over three weeks instead of arriving at once. Working with a studio well comes down to a short list of things only you can supply: a real brief, one named decision maker, a clear budget and revision count, and feedback the studio can actually act on. Get those four right and the studio spends its time designing, not guessing.

A usable brief isn't a mood board and a paragraph of adjectives. It names the audience, what they already believe about you, and the one thing you want them to walk away thinking. It lists the mandatory pieces: logo, existing brand assets, anything legal needs to sign off on. It states the budget, and whether that budget covers just building the work or launching it too. And it states how many rounds of revision are included, because a studio pricing the project is pricing the loop, not the output. "Make it feel premium" is a wish. It isn't a brief. It leaves the studio guessing at your expense, and every guess costs you a round.

Naming the budget and the revision count early is what keeps scope from getting renegotiated halfway through. A project with an agreed number of rounds has a natural end. One with an open "let's see how it looks" doesn't. That single line, three rounds, four rounds, whatever you can commit to reviewing properly, does more for the timeline than anything else in the brief.

The single biggest thing that's entirely on your side of the table is naming one person who can say yes. Studios rarely land in negative reviews over the quality of the work itself. Roughly a quarter of clients who leave a bad review for a creative agency cite communication problems and missed timelines as the reason, not the creative. A committee reviewing a logo for two weeks isn't a quality process. It's a delay with a meeting invite. One named decision maker, empowered to approve without checking back with four other people, is what removes the drift.

Feedback is the other half of this, and the difference between useful and useless feedback comes down to specificity. "The second paragraph buries the answer, move it up front" gets fixed in one pass. "Make it pop" gets fixed three times, badly, because nobody can say what "pop" means until the fourth version shows up. Good feedback names what's wrong and, where you can, why it's wrong for your audience. That isn't extra work. It's the work you're already doing when you read the draft. It just has to land on the page instead of staying in your head.

Before the first call, write down the one thing the work needs to do. Name who signs off. Pick a number of revision rounds you can actually live with. Bring those three things, and a good studio can do its best work starting with the first draft.

---

### How to make your marketing look more professional
https://kott.studio/journal/make-marketing-look-professional — Jul 2026 — Marketing
Answers: how to make my marketing look more professional; marketing design system for a small team; why does my marketing look amateur; consistent branding across marketing channels.

Marketing that looks like it comes from a big company almost never comes from a bigger budget. It comes from a system: the same few templates, the same rules for colour, type and tone, used over and over, so nothing gets invented from a blank page each time. A small team's marketing usually looks smaller because every post, every deck, every one-pager gets designed from scratch. Small decisions drift a little each time. That drift is what a reader clocks as amateur, even when any single piece looks fine on its own.

What actually changes between a polished company's output and a smaller team's is rarely talent. It's redundant decisions. A team with a system reuses a locked colour palette, a type scale, a small library of layout patterns, so whoever is making Tuesday's social post isn't also deciding what blue the brand is. A team without one remakes that decision every time. The answer comes out slightly different depending on who's at the keyboard and how much time they had.

The honest failure most small teams hit isn't a lack of taste. It's one good person holding the whole thing together in their head, or in one folder only they understand, because nobody wrote it down as a shared system. That works fine while that person is around and not too busy. It stops working the day they're on holiday, swamped with a launch, or gone. The next asset still gets made. It just quietly stops matching the last one, and usually nobody notices until a client does.

A real system is a small, specific thing: a locked set of colours and fonts, two or three layout templates that cover most of what a small team actually publishes, and a short written rule for tone so a new hire doesn't have to guess. Anyone on the team should be able to open it and produce something on brand without re-deciding the basics. That's different from paying for one polished design, which solves this week's deck and nothing after it. A system is what a studio actually builds when it's doing this job properly, and it's the part worth paying for once rather than per asset.

It's worth being honest about what that costs, because vague pricing makes the whole idea sound like a luxury. Real agency pricing surveys put a proper branding and system project commonly in the low five figures, running over several months, not a weekend job. Ongoing support is usually priced as a monthly retainer, for teams that want the system kept current rather than rebuilt from scratch every year or two. That's a bet on the volume of marketing a team expects to produce, not a one time purchase.

Here's the actual test. Hand next month's asset to whoever on the team is free that day, and see if it still looks like it belongs next to everything else. If it doesn't, that's a system gap, not a reason to hire one more designer for one more asset. Fixing the gap once is the point where it's worth bringing a studio in, so the answer stays yes without anyone having to think about it again.

---

### What an MVP really costs to build
https://kott.studio/journal/what-an-mvp-really-costs — Jul 2026 — Product
Answers: how much does it cost to build an mvp; mvp development cost; mvp budget breakdown; cost to build a minimum viable product.

A properly built MVP costs somewhere between $30,000 and $80,000, depending on what it is. Hold onto that number. It is not the $8,000 someone quotes you after a weekend with a no-code tool, and it is not the $130,000 a full custom software project averages either (Clutch). One number is too optimistic. The other is too big for what an MVP is supposed to be.

The single biggest thing that moves the price is who builds it. A US team runs $50 to $99 an hour. A team in India, the Philippines, Ukraine or Mexico runs $25 to $49 (Clutch). Product type is the second lever: a SaaS MVP typically lands at $40,000 to $80,000, a marketplace at $40,000 to $60,000, a mobile app at $30,000 to $50,000, e-commerce at $30,000 to $60,000 (Codica). Two quotes with a three times gap between them usually differ on team location and category, not on honesty.

Inside that total, the split holds up fairly consistently across studios. Discovery and research run $4,000 to $8,000. Design runs $6,000 to $10,000. The core build is $30,000 and up. Quality assurance is $8,000 to $12,000 (Codica). One studio's own worked example, a marketplace build at 1,164 hours and $50 an hour, broke down as $6,800 for design, $2,800 for architecture, $4,800 for integrations, $32,300 for core functionality, and $9,200 for project management and QA. Add 15 to 25 percent on top as a contingency, because the first estimate is never the number you land on.

Minimum was never meant to describe cheap. The term traces back to a 2001 framework from Frank Robinson, later popularised by Eric Ries and Steve Blank: the smallest version of a product that earns honest feedback from real customers before a company commits to building the rest. It is a spending strategy, not a discount. Spend the least amount required to learn whether the idea holds up, then build the rest with an answer in hand instead of a guess.

QA is the easiest line item to cut from a quote, because it happens last and there is no feature to point at when it goes well. It is also the worst place to cut. Skipping it doesn't remove the cost. It moves the cost to launch week, where a bug in front of the first real users costs more in trust than it ever saved in the budget. Skipping discovery to reach code sooner does the same thing. Both feel like savings on the invoice. Both usually show up later as a bigger bill.

A single lump sum with no line for discovery, design and QA is worth a second look before you sign it. It usually means one of two things: the studio has already decided to skip a phase, or those phases are hidden inside a total that will grow once the build starts. A quote broken into those four pieces, even roughly, is the one that tends to survive contact with the real project.

Before you sign anything, ask for the number by phase, not just the total. A studio that can hand you discovery, design, build and QA as separate lines, with a contingency sitting on top, has scoped the work. One that hands you a single figure is asking for trust it hasn't earned yet.

---

### What makes a landing page convert
https://kott.studio/journal/what-makes-a-landing-page-convert — Jul 2026 — Conversion
Answers: what makes a landing page convert; landing page conversion; landing page structure; one cta landing page.

A landing page converts when it commits to one offer and one call to action, and puts that call to action above the fold before asking the visitor to think about anything else. Most landing pages that don't work aren't ugly. They're undecided. They try to introduce the company, explain three features, and ask for an email address, all before anyone has scrolled once. Fix the structure first. Most of what looks like a copywriting problem clears up on its own.

In a survey of 37 companies building landing pages, the single factor rated most important to conversion was a clear call to action, ahead of the copywriting, ahead of the visuals. Obvious, until you look at how many pages still carry a full site navigation, a "learn more" link parked next to the actual offer, and two or three buttons competing for different jobs. Strip the nav. Pick one action. A page selling three things converts worse than three pages each selling one, because every extra option is another excuse to leave without deciding.

Eyetracking research puts 80 percent of a visitor's attention above the fold, with 57 percent of total viewing time landing on the first screenful alone. That's not a case for cramming everything into the top of the page. It's a case for deciding, in advance, which three things earn that space: a headline that states the offer plainly, one line of proof or context, and the call to action itself, visible without a scroll. The detail, the objections, the second testimonial: all of it can wait for whoever is still reading.

Google's own guidance for ad landing pages comes down to one word: relevance. The opening line has to say the same thing the ad, the email, or the link that brought the visitor there already promised. Land a click that expected a specific offer on generic homepage copy about the company's mission, and it's gone in seconds. Here's the uncomfortable version of that rule: a headline written to work for every campaign at once converts for none of them.

Landing page copy written at a fifth to seventh grade reading level converts at 11.1 percent. College level copy on the same kind of page converts at 5.3 percent, roughly half. This isn't about talking down to a marketing manager who reads well above that level. It's about cutting the extra half second a clever sentence costs someone who has already decided, subconsciously, whether to stay or go. Short sentences read as confident. Long, qualified ones read as unsure.

Mobile traffic makes up 82.9 percent of landing page visits. A one second delay in mobile load time can cost up to 20 percent of mobile conversions. That belongs in the anatomy of the page, not a technical checklist bolted on at the end. A page designed on a laptop and never opened one handed on a phone is missing a part, same as a page with no call to action above the fold.

Here's the part most small business pages get wrong, even after fixing everything above. They pick one offer, put the call to action above the fold, match the ad, write plainly, load fast, and the number still doesn't move. That's not a template problem. It means the offer itself, or the audience it's aimed at, doesn't match what the page is asking for, and no amount of button testing fixes a mismatch that deep. That's usually the point where a studio conversation is worth more than another two weeks of colour and copy tweaks.

Pull up your own landing page and check it against the five parts above, in order: one offer, the right things above the fold, a headline that matches what brought the visitor there, copy anyone can skim in a few seconds, a mobile experience that loads before someone gives up. Be honest about which one is actually missing. That's the page you have, not the one you think you built.

---

### When a website redesign is worth it, and when it just needs a fix
https://kott.studio/journal/website-redesign-worth-it — Jul 2026 — Websites
Answers: signs you need a website redesign; website redesign vs refresh; when to redesign your website; website redesign cost.

A redesign is worth it when the site is quietly costing you money. Fewer leads than it should produce. Less trust than the brand deserves. A structure too small for what the business has become. It's not worth it just because the site looks a few years old. Most owners asking whether they need a redesign are really asking a smaller question they haven't isolated yet.

The clearest sign is conversion that stays flat no matter what you try: new headlines, new buttons, a faster host, none of it moves the number. That's different from a site that simply gets less traffic than a competitor's, and it's the strongest signal a rebuild will actually help. Other honest signs: the business has outgrown the site's structure faster than the site has changed, a new shop or service bolted onto a five year old sitemap. A first time visitor couldn't find their way around without help. You're mid rebrand and the old site now argues with the new logo. Or you spend a Tuesday afternoon on three competitors' sites and realise the market has moved and yours hasn't.

None of that means a redesign is the fix. If you can point to the one thing that's broken, a confusing menu, a buried price, a slow checkout, fix that thing first and measure it before you touch anything else. One well documented case cut a site's bounce rate from 30 percent to 2.5 percent with a single change: giving visitors an obvious next step, not by touching how the site looked at all. A full rebuild that changes ten things at once leaves you no way to know which one worked. Can't name the specific problem? You're not ready to redesign anything. You're ready to go find it.

A redesign that isn't scoped carefully can cost more than the invoice. One documented case deleted about 15 percent of a site's pages during a rebuild and lost close to half its organic traffic as a result, traffic that never fully came back even after new links were built. The pages already earning you visitors are the ones a redesign is most likely to quietly kill, through a new sitemap, a renamed URL, or a page nobody thought to keep. Protect what already works before you touch what doesn't, and change the structure in stages you can actually track rather than all at once.

A proper custom redesign runs from roughly 15,000 to more than 75,000 dollars, and takes three to six months once you count planning, design, moving the old content over, and build. That range isn't a quote so much as a filter: it only earns its price against a problem large enough to justify it. A site that needs one page fixed doesn't need six months and a five figure invoice. A business that has genuinely outgrown its site does.

Still unsure which camp you're in? That's a fair place to start: a short outside audit, not a blank brief for a full rebuild. A studio that has done this before can usually tell within an hour whether you need a new site or a smaller fix to the one you have. Bring us the honest version of the problem. We'll tell you which one it actually is.

---

### What a website actually costs, from template to custom build
https://kott.studio/journal/what-a-website-actually-costs — Jul 2026 — Websites
Answers: how much does a website cost; website builder vs custom website; custom website cost; small business website pricing.

A website builder subscription runs about $10 to $50 a month. Plenty of agencies will tell you a custom build starts under $10,000. Both of those figures are true, and neither tells you what you are going to pay. The real average cost of a professionally built custom site is closer to $66,500, with a monthly retainer near $7,100 once the thing has launched and needs looking after. That gap, between the number in the ad and the number in the invoice, is the honest answer to how much does a website cost. It depends entirely on which of those two things you are buying, and most people do not find out which one until the quote arrives.

The cheap number prices a template. Someone drops your logo and copy into an existing layout, connects hosting, and you are live inside a week. The expensive number prices a decision: a site built around your business instead of the other way round, with a designer and a developer thinking through your customer, not a theme's customer. A website builder gives you a shell that a thousand other businesses are renting this same month. A custom build gets you one nobody else has. Whether that difference is worth $66,000 depends on what your business needs the site to do, not on which option sounds more responsible.

What moves the price is not the number of pages, it is the number of things the site has to do. A content management system, a shopping cart, order tracking, a login area, search, a chatbot: each one adds real engineering, not decoration. A five page brochure site and a five page site with a working checkout are not the same project, even though a client comparing quotes often assumes they are. The businesses that end up near that $66,000 average almost always have a product catalogue, an account system, or some other piece of real functionality behind the homepage. Not just more pages than a builder template allows.

Hourly rates run from under $25 an hour offshore to $200 or more at a senior studio, with most established shops in the US, Canada or Australia sitting around $100 to $149. A lower rate is not automatically the cheaper project. A team that takes three times as long at a third of the rate has billed you the same amount, and cost you two extra months getting there. The rate on the quote is not the number worth comparing. The total hours, and what the studio has shipped before, are.

The cost that catches people out is not the build, it is what comes after. A template's monthly fee is flat and it has a ceiling: you know exactly what you are paying and exactly what it will never become. A custom build's ongoing cost, that $7,100 a month average for care and small changes, is open ended, and so is what the site can grow into. One of those is a fixed expense. The other is closer to hiring a small team. Neither is the wrong choice, but only one of them is being sold to most people as if it were the other.

The honest question to ask before choosing either is whether you are shipping a fixed offer that will look the same in three years, or building something that needs to keep growing alongside the business. If it is the second one, ask a studio what the $66,000 actually buys before you compare it to a $30 a month subscription. The number means nothing without knowing what stops it from being enough in a year.

---

### How to choose a branding studio without getting burned
https://kott.studio/journal/how-to-choose-a-branding-studio — Jul 2026 — Brand
Answers: how to choose a branding studio; picking a branding agency; branding studio red flags.

Hire the studio that can show you a brand still standing up two years after it launched, not the one with the best-looking portfolio. Those are often different studios. A portfolio shows launch day, photographed kindly and cropped to flatter. What you are buying is everything after that, when the brand is being used by people who were never in the room, on things nobody made a mockup of.

You do not need a designer's eye to read a portfolio, you need three questions. Does the work change from client to client, or is every project wearing the same house style with a different name on it. Does it go past the logo into the things a business actually runs on, a website, packaging, an app, a deck, signage. And can you tell what each business was trying to say that its competitors were not. If the case studies are all a mark on a grey background and a tote bag, you are looking at a design exercise. A brand that has been through a real company has scuffs on it, and the studios who have done that work tend to show the awkward parts too.

The first call tells you more than the deck. Ask what the client had before, what changed for the business afterwards, and what the studio would do differently now. Anyone with real projects behind them will talk about the parts that went sideways, because every project has them. A studio with nothing but triumphs is either managing you or has not shipped much. Ask who does the work, as well. In a small studio the person on the call is the person who draws. In larger ones the pitch team and the delivery team are different people, and it is fair to ask which of them you are hiring.

Watch whether they ask you anything before quoting. A studio that can price a brand off a one-line email is pricing a logo, and you find that out later, when you ask for the rest of it. Proper scoping asks what you sell and to whom, who you are up against, everywhere the brand has to show up, and what it costs the business if it lands wrong. That conversation is also the best sample you will get of what working together feels like. Being asked good, slightly uncomfortable questions is the sign you want.

Some things should end the conversation. Packages sold by the number of logo concepts, because thirty options is a volume business and a good mark comes from narrowing down, not from a menu. Design contests, where dozens of strangers work for free and none of them ever asked you a question. A mood board presented as strategy. A portfolio where every project looks like whatever won awards last year, which tells you the taste is borrowed and will date on the same schedule. The subtler one is a studio that designs brands but has never built the website the brand has to live on. Identities made in a vacuum come apart the moment someone has to code them, and you end up paying a second team to quietly redraw the first team's work.

How many studios should you speak to. Fewer than you think. Three is plenty, and eight gets you a spreadsheet, a lost fortnight, and a decision made on price because everything else has blurred together. Choose the three whose past work sits closest to the job in front of you, brief them identically, and see who comes back with the better questions rather than the faster answer. Get the boring parts in writing before you sign, the deliverables, the number of revision rounds, the timeline, who owns what at the end. That is hygiene. The choice itself is made on the questions.

So write the brief before you write the emails. One page: what your business does, who you need to convince, everywhere the brand has to show up in the next year, and what it costs you if people keep misreading you. Send that same page to three studios. The one that comes back having noticed something about your business you never said out loud is the one to hire, and it is usually obvious inside the hour.

---

### How much does it cost to maintain an app after launch?
https://kott.studio/journal/cost-to-maintain-an-app — Jul 2026 — Product
Answers: how much does it cost to maintain an app; app maintenance cost per year; app maintenance budget after launch.

An app costs more to keep running than it cost to build, and most founders only budget for the build. A working app is less a thing you own outright than a thing you rent from the platforms it runs on, and the rent comes due whether you touch the code or not. A common industry rule of thumb puts yearly maintenance at fifteen to twenty-five per cent of what the app cost to make, and the first year often runs higher while the rough edges get sorted out. Over three or four years that comes to more than the original invoice. If your plan stops at launch day, it is missing most of the cost.

So what does that money buy, because maintenance sounds like fixing bugs and it is a good deal more than that. Some of it is keeping the lights on: the servers the app talks to, the services you rent to send email or take payments, the developer accounts themselves. Apple charges ninety-nine dollars a year to keep an app in its store, or the app comes down. Google charges twenty-five dollars once. Those are the small, predictable costs. The bigger ones are the work behind them: fixing what breaks, closing security holes before someone else finds them, and keeping up with the phones the app runs on.

That last part is the one people do not see coming. Apple and Google ship a major update to their operating systems every year, and each one can break something in an app that worked fine the week before. An app nobody maintains does not sit still, it rots. It starts crashing on the newest phones, then gets flagged, then gets pulled from the store for being too far behind. Leaving an app alone does not save the money, it defers a bill that grows while you look away, because a year of skipped updates is a harder and dearer job to catch up on than a year of small ones.

It helps to split the yearly cost in two, because the halves are not the same purchase. There is keeping it alive, the hosting and the fixes and the security, which is not optional and does not make the app any better. And there is making it better, the improvements you choose once real people are using it. The first is a running cost you should assume from the day you decide to build. The second is where the app earns back what you spent, and it is the part worth a real team, because it takes someone who knows the product and can tell a change that matters from one that only feels busy.

Then there is who does the work, and the cheapest-looking answer is often the expensive one. The team that built the app is usually the fastest to maintain it, because they already hold the whole thing in their heads. Handing it to a cheaper freelancer later can work, but only if the app was built cleanly enough for a stranger to pick up, and you will not know whether it was until they try. This is the quiet case for caring how an app is built in the first place. A tidy codebase is cheap to keep. A rushed one charges you every year for the corners that were cut to save money at the start.

How much should you set aside, then. Take what the build costs and plan for at least a fifth of it again each year, before you have added a single new feature. If the app is central to the business, budget nearer a third and treat the improvement as part of the product rather than an afterthought. And ask, before the build even starts, what the running cost will be, because a studio that cannot answer that has not thought past launch day.

Before you approve a number to build an app, ask for the second number: what it costs to keep running for the next three years. Put the two side by side and you have the full price of the decision, which is the one you want to be weighing. If nobody will give you that second number, better to learn it now, while it is still a conversation and not a live app slowly falling behind.

---

### Should you hire an in-house designer or use an agency?
https://kott.studio/journal/in-house-designer-or-agency — Jul 2026 — Marketing
Answers: in-house designer or agency; should i hire a designer or an agency; when to hire an in-house designer.

Whether to hire an in-house designer or use an agency comes down to one honest question most teams answer wrong: how much steady marketing design work do you actually have. If you can fill a person's week, every week, with work that sits in one lane, an in-house hire is the better buy. If the work arrives in bursts, spans brand and web and campaigns, or needs senior judgement only now and then, an agency or studio usually costs less and delivers more. Most small and mid teams overestimate how much steady work they have, and hire a full-time designer a year before they need one.

Start with what an in-house designer really costs, because the salary is the smallest part of it. A mid-weight marketing designer earns into the mid five figures a year, more in a big city or at senior level. On top of that you carry the things nobody quotes you: the software and font licences, the recruiting to find them, the kit, and the management time to brief and review their work. Add it up and the true cost of a seat lands well above the salary line, and that is before they have made a single thing. A quiet extra cost comes with it too. One hire is one person, with one skill set and one taste, and no one to catch it when either drifts.

What that hire buys you, when the volume is there, is availability and context. Someone in the room who knows the product, turns work round the same day, sits in the meetings, and carries the brand until applying it is second nature. For high, steady output, nobody beats a good in-house designer on cost per asset or on speed. The catch is range. A designer who is brilliant at social graphics is often not the person to redraw your brand or build your site, because those are different jobs that happen to share a job title.

An agency or studio buys you the opposite: range and senior judgement without a full-time salary attached to it. You get a group of people, one who thinks in brand, one who builds, one who art-directs, and you dip into whichever the work needs instead of hoping your one hire covers all of it. You pay more per hour and, when the work is lumpy, less per year. You also get a second opinion built in, which the team of one never has. The trade is that you are not first in the queue and you have to brief people who are not in your standups, so the relationship needs running.

Most teams that get this right end up with a mix, and it is worth naming because it is the answer people arrive at slowly and expensively. A junior or mid designer in-house handles the daily volume, the posts and slides and endless resizing, and a studio is kept on call for the work that sets the direction, the brand, the website, the campaign or launch that has to land. The costly mistake is getting that split backwards: paying a senior full-time salary to resize banners, or inventing your own brand from a blank page to dodge a fee and living with the result for years.

So how do you tell which side you are on before you commit. Count the hours honestly. If you cannot point to twenty or more hours of real design work a week that will still exist in six months, you do not have a full-time role, you have a part-time one you are about to overpay for with a salary. Then look at range. If it is a lot of one kind of thing, a hire makes sense. If it is a little of everything, or the work that matters most is the occasional piece that has to be right, that is a studio's shape, not an employee's.

Before you write the job advert or sign the retainer, put two things on paper: the honest weekly hours of design work that will still be there in six months, and the spread of skills it actually needs. A lot of one thing points to a hire. Some of everything, or a few things that simply have to be right, points to a studio. And if you cannot tell yet, lean to the studio first, because a retainer you can end in a month is a far cheaper thing to be wrong about than a full-time hire you have to let go.

---

### When a design project ends, what do you actually own?
https://kott.studio/journal/what-you-own-after-a-project — Jul 2026 — Studio
Answers: who owns design files after a project; design project ownership and copyright; what to ask before signing with a design studio.

When a design project ends, you own less than you might think, unless the contract says otherwise. The finished logo or website is yours to use, but the working files behind it, the copyright to the design, and sometimes the fonts and the code can all stay with the studio by default. That is not a scam. It is what happens when nobody spells it out, and it is the thing to settle before you sign, not after the last invoice clears.

Start with the difference between the finished thing and the thing that made it. A studio hands over the exports: the logo as a PNG and an SVG, the website live on your domain, the deck as a PDF. What it does not always hand over is the editable source, the layered logo file, the design file the site was built from, the original artwork. You can use the exports anywhere. You cannot change them, or take them to another designer to build on, without the source. If you want the ability to edit and extend later, that has to be named as a deliverable, because it is often treated as the studio's own working material and priced separately.

Then there is who owns the copyright, which is a separate thing from who holds the files. In a lot of places the person who makes a creative work owns the rights to it by default, even after you have paid, until those rights are transferred to you in writing. So you can pay in full for a logo and still not own the copyright unless the agreement assigns it to you. A good studio transfers the rights to the final identity as a matter of course and says so plainly. If your contract is silent on it, ask, because permission to use something is not the same as owning it, and the gap shows up the day you try to register your own logo as a trademark.

Fonts are the trap almost nobody checks. The typeface in your brand is rarely owned, it is licensed, and the licence has terms: how many people may use it, whether it covers your website as well as print, sometimes a fee that renews every year. When a studio picks a font for you, you inherit that licence and whatever it costs. Get it in writing which fonts your brand depends on, whether the licence is in your name or the studio's, and what it actually covers, or you can find out a year later that the font on your own site was never cleared to be there.

For anything built, code or a whole website, the question is whether you can pick it up and run it somewhere else. Custom code written for you should be handed over and hostable anywhere. A site built on a studio's own proprietary platform, or tied to their hosting, is a different arrangement: it works beautifully right up until you want to leave, and then you learn you were renting, not owning. Ask plainly whether you can move the site to another host or another team without a rebuild. If the answer is no, that is not automatically the wrong choice, but you should know you are making it.

Two small things people hand over without a thought and then regret. Your domain name and your hosting and analytics accounts should be registered in your name, with you as the owner, not sitting inside the studio's account with you as a guest. It is convenient to let the studio set everything up under their login, right up to the day you part ways and find the address your customers type belongs to someone else. Set those up in your own name from the start and give the studio access, rather than the other way round.

None of this needs a lawyer to fix. It needs one honest paragraph in the agreement before work starts, covering five things: which source files you receive, that the copyright in the final work transfers to you, which fonts are licensed and to whom, whether the build is yours to host anywhere, and that the domain and accounts are in your name. A studio worth hiring will have those answers ready and put them in writing without flinching, because it has had the conversation before. If a studio goes vague when you ask who owns what at the end, you have learned something useful about them while it still costs you nothing. Ask the question before you sign, not when you are trying to leave.

---

### How many pages does a small business website need?
https://kott.studio/journal/how-many-pages-a-website-needs — Jul 2026 — Websites
Answers: how many pages should a website have; small business website pages; one page website vs multi page.

A small business website does its whole job in about five pages, and the number is the wrong thing to worry about. What goes on each page, and the order a stranger meets them in, is the decision that actually matters, and it is the one most people skip while they argue over how many pages to have. So the useful question is not how big your site should be. It is which pages earn their place, and which are there because a template had a slot for them.

Start with the set that nearly every small business needs. A home page that says what you do, who it is for, and what to do next. A page on what you actually offer. Something that proves you can do it, whether that is your work or a couple of real results. A page on who is behind the business, because people buy from people they can place. And a way to get in touch. That is most sites, in full. Each of those pages is there because a real visitor needs it to decide, not because a bigger site looks more serious.

The pages that cause trouble are the ones that pile up without anyone deciding to add them. A separate page for every service you offer. A page for each person on the team. A news feed last touched two years ago. A resources section nobody opens. Each one felt responsible at the time and now sits there as upkeep you owe forever, splitting both your attention and the visitor's. A site does not become more credible by getting bigger. Usually it goes the other way, and the two pages that actually bring in work end up buried under the ones that do not.

The obvious worry is search: surely more pages mean more chances to rank. Only the right pages do. A page helps you in Google when it genuinely answers something a customer types, and hurts you when it is thin and only there to pad the menu. Ten near-empty service pages work against you. A few pages that each cover a real question work for you. A blog is the same bargain written large: worth real money if you will actually feed it, dead weight the moment you stop. Add a page for a reason you can say out loud, never to reach a number.

Then there is the one-page site, which is a fair call more often than people expect. If you have a single offer and one kind of customer, a single scrolling page can do everything a five-page site would, faster and cheaper. It starts to cost you the day you need to rank for more than your own name, or you pick up a second type of customer who needs a different pitch. Pick the shape from what your visitor has to do, not from a rule about how real websites look.

The count, then, is the easy part. Anyone can write down five page names in a minute. The work worth paying for is deciding what belongs on each page and in what order a stranger meets it. That is information architecture, and it is invisible when it is right and costly when it is wrong. Done well, a visitor lands and finds the one thing they came for without having to think. Done badly, you have five tidy pages and an empty inbox, which is exactly where a lot of homemade sites quietly sit.

So before you brief a build, or start dragging boxes around in a builder, do not begin with a list of pages. Write down the handful of things a visitor must be able to do on your site, then work out the fewest pages that let them do it. If that comes to five, build five and stop. If you cannot tell whether a page earns its place or just feels like one a proper business ought to have, that is the judgement worth borrowing from someone who has watched which pages bring in work and which only ever sit there.

---

### Should your ads point to your homepage or a landing page?
https://kott.studio/journal/ads-homepage-or-landing-page — Jul 2026 — Conversion
Answers: should ads go to homepage or landing page; dedicated landing page for ads; landing page vs homepage.

Send your paid traffic to a page built for that one ad, not to your homepage. It is the cheapest improvement most ad budgets have available, and it is the one teams skip because pointing the ad at the homepage is one less thing to build. The homepage is the wrong destination for a plain reason: it was built to serve everyone who might ever land on it, and an ad click is not everyone. It is one person who was just promised one specific thing.

A homepage has to do a dozen jobs at once. It introduces the company, lists everything you offer, and points off to your about page, your pricing, and your careers, all while trying to be useful to a customer, a job seeker, and a supplier on the same screen. That is a fair design for someone who arrived by typing your name into Google. It is a poor one for someone who clicked an ad about a single product, because the thing they were promised is now one option among fifteen, and they have to go hunting for it. Most people do not hunt. They leave.

A landing page is the opposite by design. It makes the one promise the ad made, in the same words, and it gives the visitor one thing to do about it. No full navigation menu inviting them back out, no competing offers, nothing on the page that is not there to move that one click forward. The page and the ad read as a single continuous thought, so the person who clicked never has that half-second of "this is not quite what I expected" that loses the sale. That continuity is the mechanism. It is not decoration.

There are times the homepage is the right call, and it is worth being honest about them. If the ad is a search for your own company name, the homepage is exactly what that person came for. If your budget is small and you have no dedicated page built yet, sending clicks to a clear homepage beats sitting out while you wait to build the perfect one. And if you sell a single product and your homepage already behaves like a landing page for it, a second page may be effort you do not need. The rule is a strong default, not a law.

The next question is usually how many landing pages you need, and it is fewer than the internet implies. You want one page per distinct promise, not one per keyword. If three ads sell the same offer to the same kind of buyer, they can share a page. If one campaign talks to freelancers and another to finance teams, those are two different promises and want two pages, because the words that land with one fall flat with the other. Build to the number of real audiences you have, not to the length of your keyword list.

People worry these pages will drag down their search ranking. They will not, because ranking is not their job. A paid landing page exists to catch ad clicks, and it does not need to appear in Google at all. Your SEO pages are a separate set with a separate purpose, and keeping the two apart helps both. The landing page can be single-minded about converting the click without also trying to please a search engine, and the pages you do want ranked stay written for the people who find you by searching.

Where this stops being a weekend job is at volume and over time. One landing page is quick. Keeping a dozen of them live, each matched to a running ad, each on brand, each fast on the phone most clicks come from, and each measured against the version before it, is a standing piece of work, and it is where a good page pulls ahead of a passable one. That is the part worth handing over, because a page that lifts the conversion rate a few points pays for itself against the ad spend running through it. Before you raise your budget, do the free check first. Click your own ad, see where it drops you, and ask whether that page repeats the exact promise you paid for and offers one obvious thing to do. If it lands you on the homepage, you have found money you are already spending and not collecting.

---

### How long a rebrand takes, and why rushing it costs you
https://kott.studio/journal/how-long-a-rebrand-takes — Jul 2026 — Brand
Answers: how long does a rebrand take; rebrand timeline; rebranding process steps.

A rebrand for a small business usually takes six to twelve weeks. A full rebrand for a larger company, with strategy, naming, and a wide rollout, runs three to six months, sometimes longer than that. The calendar is not really the point though. Most of that time is thinking, not drawing, and the parts you can cut to go faster are the parts that make a rebrand worth doing at all. So the question worth asking is what those weeks are actually buying you.

Here is the honest shape of where the time goes. The first stretch is not design. It is working out what the brand should say and who it is for, before anyone opens a design tool. Then the identity itself gets made: the mark, the type, the colour, and the system that holds them together, drawn and tested and revised. Then everything the brand touches gets rebuilt to match, from the website and the templates to the profiles and the sign on the door. The bit people picture as the rebrand is the middle third. The thinking before it and the rollout after it are where the weeks really go, and they are the parts that decide whether the new look means anything.

Most of what sets your timeline sits on your side of the table, not the studio's. Two things move it more than anything else: how fast you give feedback, and how many people have to agree before a decision sticks. A founder who can approve a direction in a day keeps a rebrand tight. A committee that meets every second week turns eight weeks into five months, and none of the extra time is design work. Before you ask how quick a studio is, look honestly at how quickly your own side can make a call, because that is the clock that usually runs slow.

Scope is the other lever, and it pays to be clear about which job you actually have. A refresh that keeps your name and the core idea and just updates how it all looks is the quick end, often a handful of weeks. A full rebrand that reopens the name, the positioning, and the whole system takes longer, because there is more to decide and more to get wrong. Deciding which of the two you need is a separate question worth settling before you brief anyone, because the two run on completely different clocks.

You can compress a rebrand, and it tends to show. The cost of rushing is not a rougher logo. It is skipping the work at the start where you settle what the brand is even for, so you pay full price for a fresh coat of paint over the same confusion. Or it is launching the new look everywhere in a single weekend with no plan, so half your customers think they have wandered onto the wrong company and your search ranking takes a knock you never budgeted for. A rebrand that lands in a week has usually had its most expensive part quietly removed, and that part was the thing you were paying for.

You do not have to switch everything on in one day, and usually you should not. A sensible rollout goes in the order your customers notice: the website and the main profiles first, then the templates and documents, then the slow physical things as they come up for renewal. Phasing spreads the cost and the disruption, and a wrong turn gets caught on one surface instead of all of them at once. It does add calendar time, which is the trade. Decide up front whether you want it fast and all at once, or steady and staged.

So before you ask a studio how quickly they can turn a rebrand around, do two things first. Settle whether you need a refresh or the full job, since they run on different clocks. Then look hard at how fast your own side can give feedback and make decisions, because that is what really sets the pace. A studio worth hiring gives you a real timeline with the thinking built in, not the fastest number you want to hear. If someone promises a full rebrand in a few days, that is not speed. It is the tell that the important, expensive part has been left out.

---

### How to decide what goes in your MVP, and what to cut
https://kott.studio/journal/how-to-scope-your-mvp — Jul 2026 — Product
Answers: how to scope an mvp; mvp scope for startup; what to build first in an mvp.

An MVP is not a smaller version of the product you want to build. It is the smallest thing that tests the one assumption your business is riskiest on. Most founders get this backwards and build a shrunken version of the whole vision, which is how three months and a real chunk of budget go into features nobody has asked to use yet. The question worth answering is not what to put in your first version. It is what you can leave out and still learn whether the idea works.

The test for what stays is narrow. Keep only what a user needs to complete the core action once, and what you need to see whether they did. Anything a user does not touch on the way through that single loop can wait. If your product is a marketplace, the loop is one person listing a thing and one person buying it. If it is a tool, the loop is a user doing the one job they came for and coming back to do it again. Draw that loop first, then be suspicious of everything that is not on it.

So what actually gets cut. In practice the first things to go are the ones that feel responsible to build: the account settings page, the polished onboarding, the admin dashboard for yourself, the second type of user, the integrations you might want later, the edge cases nobody has hit yet. You can fake or skip almost all of it at the start. Handle sign-ups by hand. Run the admin side off a spreadsheet. Support one kind of user, not three. None of that is how the product works forever. It is how you find out whether there should be a forever.

Small scope is not the same as rough work, and this is where the advice to "just ship something" leads people wrong. Doing one thing is the discipline. Doing it badly is a different mistake, and a costly one, because a clumsy first version teaches you nothing you can use: people leave and you cannot tell whether the idea failed or the execution did. Cut the number of things you build. Do not cut the quality of the few you keep. The one screen a user actually sees has to work and has to be clear, or the test is contaminated before it starts.

Scope does not creep at the planning stage. It creeps during the build, one reasonable-sounding request at a time. The guard is to write the single assumption down before anyone starts, in one sentence, and hold every new feature up against it: does this help us learn whether that is true, or is it here because it would be nice to have. Most things are nice to have. A team worth hiring will push back on scope you do not need, and that pushback is a sign of a good studio, not friction. If everyone on the build says yes to everything, the budget finds its ceiling fast and you are no wiser at the end of it.

The rest gets built after the loop proves out, in response to what real users do, not the roadmap you wrote before launch. That is the actual payoff of keeping the first version small. You reach the evidence sooner and cheaply, and the second version is shaped by facts instead of guesses. A founder who spends a few thousand learning that the core loop works has bought something real. A founder who spends fifty thousand building the full vision before anyone has used it has bought a guess with a nice finish.

So before you brief a build, do the harder half of the work. Write the one assumption your idea lives or dies on, draw the single loop that tests it, and list everything you are choosing not to build yet. That list is the most valuable thing in the project and the easiest to get wrong on your own, because cutting your own ideas is hard and knowing which cut is safe takes having watched a few of these ship. If you want a second pair of eyes on where the line falls, that is the conversation to have before the building starts, not after the budget is half gone.

---

### What to put on a product launch page, and when to build it
https://kott.studio/journal/when-to-build-your-launch-page — Jul 2026 — Marketing
Answers: product launch page; what to put on a launch page; pre-launch landing page; coming soon page.

A product launch page should be live weeks before you launch, not thrown together in launch week. Most of its work happens before launch day. It catches the interest your teasers stir up and gives every email and post one place to point. It also tells you whether anyone wants the thing before you have bet the quarter on it. The page you build the night before the announcement is the one working hardest on the day it can least afford to be rough. So the question worth answering is not what a launch page looks like. It is what it has to do at each stage, and how early you have to start for it to do any of it.

A launch page does two jobs, and most teams only build the second. Before launch it is a capture page: a clear promise, one line on who it is for, and a single cheap action, usually leaving an email. After launch it turns into the buy or sign-up page, the same promise but with the product real, proof it works, and a way to actually pay. Build only the launch-day version and you have thrown away the weeks when you could have been gathering the audience you launch to.

What the page needs on launch day is a short list, and it barely changes from product to product. A headline that says what it does in the words your buyer would use, not the name you use for it internally. A line on who it is for. The single most convincing thing you can show, whether that is a ten-second demo or one real result. One action, with nothing on the page competing with it. And the obvious objection or two answered right there: does it actually work, what does it cost. Most of what teams add beyond that is there to reassure the team, not the visitor.

How early should the first version go up? The moment you can describe the product in one honest sentence, which is usually weeks before it is done. An early page earns its place twice over while you build. It collects an audience you can launch straight to instead of launching into silence, and the sign-ups tell you whether the idea has legs before the code is even finished. Putting it up early is not about polish. It is the difference between launch day meeting a warm list and launch day being the first time anyone has heard of you.

The common mistake is treating the coming-soon page and the launch page as one job you do once. They share a look, not a purpose. A coming-soon page that just says big things coming over a logo collects nothing, because it gives a stranger no reason to hand over an email. It has to make the same clear promise the finished page will, only without the product to point at yet. And the switch from one to the other wants planning, because the worst time to be rewriting your headline is while the announcement is already going out.

None of this is hard to list, and all of it is hard to get right against a deadline. The headline that makes a stranger care. The one thing worth showing, out of everything you could put up. Whether the page loads fast and reads clearly on the phone most people will open it on. Those are the calls that decide whether the traffic you fought for turns into anything, and they are the first to get rushed when the page is a launch-week job. A launch is the one moment a mediocre page costs you most, because everything you have built funnels through it on a day you do not get to run again. That is the argument for building it early, and for not building it alone when the launch actually matters.

So before you plan the launch, plan the page, and plan it in two stages. Settle the one sentence that describes the product, put a pre-launch page up now to start collecting interest, and decide in advance what changes on the day. If the launch is small, that is a weekend of your own time, well spent. If it is the launch the business is counting on, the page deserves the same care as the product behind it, and that is a conversation worth having well before launch week rather than during it.

---

### How much a design studio costs, and how to read the quote
https://kott.studio/journal/how-much-a-design-studio-costs — Jul 2026 — Studio
Answers: how much does a design studio cost; design agency pricing; how to read a design quote.

A design studio costs anywhere from a few thousand to well into five or six figures, and the spread is not a mystery. It is the difference in what you are actually buying. Two quotes for a new website can sit five times apart and both be fair, because they are quietly pricing different jobs, different people, and different amounts of the hard thinking. So the useful skill is not hunting for the lowest number. It is reading a quote well enough to know what each one actually contains.

It helps to have a rough shape. Small studio project work usually starts in the low thousands for something tight and climbs into the tens of thousands for a full brand or a custom site a business runs on. Larger studios and agencies begin about where the small ones top out. A freelancer sits below all of it. None of those is the correct price. A five thousand quote and a thirty thousand quote can both be honest, because they answer different questions about how much of the work and the risk you want to hand over.

The reason two quotes differ so much is almost never greed. It is scope you cannot see. One studio prices the screens you asked for. The other prices those screens plus the states nobody mentioned, the empty inbox, the error message, the phone version, the loading, plus the build, plus a round of changes, plus someone to own it when it breaks after launch. On paper both say website. In practice one is a picture and the other is a working thing. The cheaper quote only wins if both describe the same delivery, and they rarely do.

Studios charge in one of three ways, and the method itself tells you something. A fixed project fee means they have scoped the work and will carry the risk of it running long, so you get a number you can plan around and you pay for that certainty. An hourly or day rate puts the risk back on you: cheap if the job is small and clear, open-ended if it is not. A monthly retainer buys a slice of the team on tap, which suits ongoing marketing work more than a one-off build. If a quote will not say which of the three it is, that is the first thing to ask.

A quote you can actually compare says five things plainly. What is included, down to the awkward details. Who does the work, the person you met or a junior you never will. How many rounds of changes before the price moves. Who owns the files and the code at the end. And how long it takes. A quote missing any of those is not cheaper, it is vaguer, and the gaps come back as invoices later. Ask for the five before you put two quotes next to each other, or you are comparing a real plan against a hopeful one.

The cheapest quote is not automatically wrong, but it is the one to read hardest. Sometimes low means efficient. More often it means the hard parts are missing and will return as extras, or that the work will be done by someone learning on your budget. A higher number earns its keep when the thing has to carry the business, when it has to convert, rank, scale, and still be standing in two years. Paying studio rates for a job a freelancer could do is a waste. Paying freelancer rates for a job that needed a studio is a rebuild you pay for twice.

So before you compare a single number, write down what you are actually buying: the outcome you need, not the deliverable you assume produces it. Then ask every studio for the same five things in writing and read the quotes side by side. The one that looks dearer often costs less by the end, because it counted the work the cheap one left for you to find. And if a studio cannot tell you plainly what its number includes, you have learned the most useful thing about working with them before paying a penny.

---

### When a website builder is enough, and when it starts costing you
https://kott.studio/journal/website-builder-vs-custom-build — Jul 2026 — Websites
Answers: website builder vs custom website; custom website vs website builder; when to move off squarespace or wix.

A website builder like Squarespace or Wix is the right choice far more often than a studio will admit, right up until your website has to do real work. The honest question is not builder or custom in the abstract. It is whether your site is a business card or a salesperson, because those two jobs need completely different things and cost completely different amounts.

A builder is genuinely enough when the site's job is to exist and be found. You have a handful of pages, you will change them rarely, and nobody picks you over a competitor because of the website itself. For that, a builder is hard to beat. It runs under twenty dollars a month at the entry level, a little more on the plan a real business actually needs, and you can have something respectable live over a weekend. Paying a studio a few thousand for the same result would be lighting money on fire.

It starts costing you the moment the website has to earn its keep. When customers compare you against two rivals before they decide, the site becomes part of the pitch, and a template a stranger half-recognises does you no favours. When it has to rank, load fast on a phone, and connect to your booking or payment system without a pile of paid add-ons, the thing that made the easy version easy turns into the thing you fight. You lose evenings forcing the builder to do what it was never built for, and it still looks like the template underneath. That is the real bill: not the monthly fee, but the ceiling.

The pitch of a builder is that anyone can make a website, and that part is true. The tool is easy. The decisions are not. What goes at the top of the page, what to leave out, which words make a stranger stay, where the single button belongs: none of that gets easier because the software is friendly. Plenty of businesses build their own site on a builder and end up with something tidy that still brings in no work, because the hard part was never the dragging and dropping. A builder saves you the cost of construction. It does not save you the cost of knowing what to build.

You can start on a builder and move to a custom build later, and for a lot of businesses that is the right order. Prove the thing works, learn what your customers actually respond to, then build properly once you know. The mistake is planting your whole business on a builder while quietly knowing you will outgrow it within a year, then finding that moving off means rebuilding from scratch and redoing the search ranking you had going. Starting cheap is smart. Treating the cheap version as permanent when it is not is the costly part.

On the sticker, custom is dearer. A build from a professional usually starts in the low thousands and climbs into five figures for anything a real business leans on, against a subscription that costs less than lunch. Compare the total, though, not the first invoice. The true cost of the builder is the monthly fee, plus every hour you and your team spend wrestling it, plus the customers you lose to a site that loads slowly or says the wrong thing, plus the rebuild when you finally outgrow it. Sometimes that still comes to less than a custom build. Often, for a business whose website is how it wins customers, it comes to more.

So before you choose, write one line: what your website has to do for the business. If the answer is let people find us and get in touch, open a builder today and do not feel a flicker of guilt. If the answer is win us work against competitors who are all online too, you have outgrown the question, and that is worth a conversation with someone who builds sites made to earn their place.

---

### Should you show your prices on your website?
https://kott.studio/journal/showing-prices-on-your-website — Jul 2026 — Conversion
Answers: should you show prices on your website; showing prices on a service website; pricing page for services.

Show a price, or at least an honest starting range. Hiding it behind "contact us for a quote" feels safe, and for most small businesses it quietly costs you the leads you actually want, because a serious buyer comparing options leaves the moment they cannot tell whether you are in their budget. The question worth arguing is not whether to show a number, but which one, and how you frame it.

When a page has no price, the visitor fills the gap with a guess, and the guess is rarely kind. Some decide you must be expensive and leave without asking. Others carry on assuming you are cheap and feel misled when the quote finally lands. Both have half-left already, and the competitor who simply printed a number gets the enquiry instead. A visible price does your qualifying for you: the people who can afford you lean in, and the ones who never could stop booking calls that were never going to close.

The usual objection is that competitors will see it. They will, and it matters far less than it feels like it should. A rival can already ring up pretending to be a customer, and the ones worth worrying about know the going rate anyway. You are not keeping the price from your competitors, you are keeping it from buyers, and only the buyers were ever going to pay you. If the entire advantage of your business is a number nobody can see, the number was never the advantage.

If your price is high, showing it is still usually right, you just cannot show it naked. A figure on its own invites sticker shock. The same figure sitting beside what it includes and who it is for reads as a considered price rather than a random one. The client who walks away from an honest number was not going to turn into a happy customer once they discovered it three calls deep. Better they rule themselves out on the first visit, while it costs neither of you anything.

The harder case is genuinely bespoke work, where a single figure would be a lie. You still owe the visitor an anchor. A starting-from figure, or a worked example like "a site like this usually lands in the low thousands", gives a stranger enough to place themselves without pretending every job is identical. "It depends" is true and useless. "It depends, and here is roughly where it tends to land" is true and helpful. All you are trying to do is let someone know within ten seconds whether to keep reading or quietly move on.

There is one real exception. If you sell mostly to large organisations where every deal is negotiated, procurement expects a tailored quote, and a public figure would only anchor you low against contracts worth far more, then keep it off the page and qualify in conversation. That is a deliberate call for a specific market. It is not the same as a local business or a small studio hiding a price because naming it out loud feels frightening. Be honest with yourself about which of those you actually are.

So before you reach for "contact us for pricing", decide what a stranger should be able to work out in their first ten seconds on the page: roughly what you cost, and whether that is meant for someone like them. The harder part, and where most pages come undone, is putting that number on the page so it qualifies the right buyers instead of scaring everyone off, with the context that makes a fair price read as fair. That is a design and copy problem as much as a pricing one, and it rewards someone who has watched it work and fail on real pages. Make the number visible first. Make it land well next.

---

### Does your business actually need a rebrand, or just a tidy-up?
https://kott.studio/journal/does-your-business-need-a-rebrand — Jul 2026 — Brand
Answers: does my business need a rebrand; signs it's time to rebrand; rebrand or brand refresh.

Most businesses that ask for a rebrand do not need one. They need a refresh, which is a different job at a fraction of the cost. A rebrand changes who you are. A refresh changes how you look. Working out which problem you have is the whole decision, and getting it wrong is where the money goes.

A refresh keeps your name, the core idea of your logo, and whatever recognition you have built up, and it updates the execution: the typography, the colour, the website, the templates that have drifted out of line. A rebrand goes deeper. It reopens the name, the positioning, the mark, the whole system, and it accepts that people will have to learn you again. One is a tune-up. The other is a reset. They cost different amounts and carry different risks, so the first thing to settle is which one your problem actually calls for.

You need the full rebrand when the identity itself is wrong, not just tired. There are three honest triggers. You have changed what you do, so the name or the promise no longer describes the business. There is a reason recognition should reset, like a merger, a legal fight over the name, or an association you need to leave behind. Or the brand plainly misrepresents you, and the right customers walk past because you read as cheaper or smaller than you are. If one of those is true, tidying the surface will not fix it.

Most of the time it is the other case. The brand still fits who you are, it has just aged or gone inconsistent. The logo is fine but the website is five years old. Every person on the team applies the colours a little differently because there was never a real system to follow. It looks improvised, not wrong. That is a refresh, and treating it as a rebrand means paying to throw away recognition you spent years building, then paying again to build it back.

So the test is one question. Is the problem what your brand says, or how well it is applied? If a stranger understands what you do and who it is for, and the only trouble is that it looks dated or scattered, you want a refresh. If a stranger comes away with the wrong idea of what you are, or the name itself works against you, you want the deeper job. Answer that honestly before anyone sends you a quote, because the two are priced and planned in completely different ways.

Roughly, a refresh is the smaller piece of work: cleaning up the identity, rebuilding the site, and handing you a system you can actually keep to. A full rebrand costs more, because the thinking at the front, what you stand for and what the name and mark should be, is the expensive part and the part you cannot skip. Neither is a job for your most junior hire or a marketplace logo. The costly mistake is not the fee. It is choosing the wrong one: a rebrand you never needed, or another refresh painted over a foundation that was already broken.

Before you brief anyone, write one sentence: what a stranger gets wrong about you today. If the answer is nothing, it just looks tired, brief a refresh and protect what you have. If the answer is they think we are something we are not, you have a rebrand on your hands, and that is the conversation worth having with a studio before you spend on either.

---

### Who should build your MVP: agency, freelancer, or cofounder?
https://kott.studio/journal/who-should-build-your-mvp — Jul 2026 — Product
Answers: who should build your mvp; hire an agency or freelancer for mvp; agency vs freelancer vs technical cofounder.

There is no single best way to build an MVP. The right choice comes down to two questions almost nobody asks first: do you have money to spend or equity to give away, and can you tell good code from bad. Answer those honestly and the decision between an agency or studio, a freelancer, and a technical cofounder mostly makes itself.

Rough numbers, because they matter. A freelancer usually charges somewhere between fifty and a hundred and fifty dollars an hour, and a simple MVP lands around three to fifteen thousand depending on scope and who you hire. A studio costs more on the sticker, often fifteen thousand at the low end and comfortably past fifty for anything a real product needs, and it arrives as one accountable team. A technical cofounder costs no cash at all, which is exactly why founders reach for it, and a slice of the company forever, which is why they later wish they had thought harder.

Start with the cofounder, because it is the option people pick for the wrong reason. A cofounder is not a cheaper developer. It is a partner you cannot easily part with, holding a slice of the company that is hard to claw back. If the person is genuinely great, shares the risk, and will still be building in two years, that equity is the best money you never spent. If you are giving away a quarter of the company because you did not want to pay for a build, you have made the most expensive decision in the project to save on the cheapest one. Give equity for commitment, not for code.

A freelancer is the right call when you can judge the work. If you can read a pull request, or you have someone you trust who can, a good freelancer is the best value on this list. The trap is the non-technical founder who hires cheap, cannot tell whether the code is sound, and finds out at launch that it will not scale or cannot be handed to anyone else. That is the ten-thousand-dollar build that becomes a twenty-five-thousand-dollar rebuild. Cheap is only cheap if you can check it.

A studio wins on total cost more often than the sticker suggests, and it is usually the honest answer for a founder who is not technical. You are paying to remove the coordination that quietly eats a freelancer budget: the founder hours spent managing, the scope that drifts, the testing nobody owned, the rebuild when the first version cannot carry the second. One team that designs and builds together, and that you can call when something breaks after launch, is calmer and often cheaper by the time the product actually ships. The trade is capacity and control. A good studio takes fewer projects and will push back on scope you do not need.

So the test is not which option is cheapest today. It is which one gets you a working, shippable product you still own and can build on. If you have cash and cannot evaluate code, take the studio. If you can evaluate code, or you have thin cash and a real technical hire willing to commit, a freelancer or a cofounder can be the better buy. What you should not do is give away equity, or chase the cheapest hours, to dodge a bill you could actually afford.

Before you talk to anyone, write down two things: what the MVP has to do for you to know the idea works, and how you will tell whether the build is any good. The first keeps the scope small enough to afford. The second decides who you can safely hire. Get both on paper and the quotes stop looking like a gamble.

---

### How much of your brand you can run without a designer, and where that stops
https://kott.studio/journal/on-brand-without-a-designer — Jul 2026 — Marketing
Answers: how to stay on brand without a designer; brand consistency for small teams; marketing design without a designer.

You can run most of your brand day to day without a designer. What you cannot do without one is create the thing you are keeping consistent in the first place, or fix it once it drifts. So the honest split is this: a designer builds the system and the pieces that set the direction, and your team runs the everyday output inside it. Get that division wrong in either direction and you either overpay or slowly go off brand.

Here is what a team can genuinely handle alone, once the system exists: the weekly social posts, the slides, the email headers, the small things you make constantly. That works because someone already made the decisions that matter and handed you templates to fill in. A lightweight brand system is the handful of fixed choices that make it safe: your logo in the formats you use, two or three colours with exact values, one or two fonts and where to get them, and real templates for the things you ship every week, all in one place the team can open.

Here is where doing it yourself quietly costs you. The system itself is not a DIY job. Pulling colours off your old site and picking a font that feels nice is how brands end up looking like everyone else, because the choices that make an identity yours are exactly the ones that are hard to make well. The same goes for anything that becomes the reference everyone copies: get the master template wrong and every asset built on it is wrong too, at scale, for a year. That is the work worth paying for, because it is the work that is expensive to get wrong.

So bring in a designer for the decisions, not the volume. The identity, the template system, a launch that has to land, a rebrand, the moment you outgrow the look you started with. These set the direction everything else follows. If you are paying a designer to resize the same banner every week, you have a system problem. If you are inventing your own identity from a blank page to save the fee, you have the opposite problem, and it usually shows.

Even with a good system, brands slip off course quietly: a slightly wrong blue, a downloaded font, a photo stretched out of shape. Keep one source of truth for the assets so nobody rebuilds from memory, and have someone review the templates every few months. But be clear about what that maintenance cannot do. It keeps you consistent, it does not make you better, and it will not tell you when the whole look has aged out. That judgement is why you keep a studio's number.

So run the day to day yourself, and do not apologise for it. Just know the line. The output is yours to make. The system underneath it, and the calls that reshape it, are worth a studio. If your brand is starting to feel improvised, or you are about to build the templates the rest of the company will copy from, that is not a job for your most junior hire. That is the part we would want to get right with you.

---

### Design and build under one roof: what actually changes
https://kott.studio/journal/design-and-build-under-one-roof — Jul 2026 — Studio
Answers: design and development studio; design and build agency; one team for design and development.

Most studios draw a beautiful website and hand the files to a separate development shop to build. The seams between those two teams are where projects quietly fail: the design that could not quite be built, the interaction that got value-engineered out, the launch that slipped because each side was waiting on the other. Putting design and build in one team removes the seam. That is the whole point, and it changes more than it sounds.

Here is what the seam looks like in practice. A designer specifies a smooth page transition, the separate developer says it is out of scope or too slow, and three weeks later you approve a build that feels nothing like the mockup you signed off. Nobody lied. The design just assumed things the build could not honour, and there was no one who owned both. When the people who decide how it looks are the people who make it work, that gap closes before it is ever drawn.

The obvious worry is that one team costs more or moves slower. In our experience it is the opposite on both counts. Fewer handoffs means fewer review cycles, fewer rounds of "that is not what we meant", and no time lost translating a design file into a written spec for someone who was not in the room. You are paying for one conversation instead of managing two vendors who blame each other when something is off.

If you already have a developer you trust, you do not need to replace them. What you want from a studio in that case is design that arrives as a real, buildable spec: components, states, and edge cases, not just pretty screens. Ask for that in writing. The trouble only starts when a studio hands over static mockups and treats the rest as someone else's problem.

Plenty of studios say "we do development too" and then quietly subcontract it, which puts the seam right back. To check before you sign, ask three things: who actually writes the code, whether you can see recent work they built and shipped rather than only designed, and who you will talk to when something breaks after launch. If the answer to that last one is vague, the gap is still there, just hidden from you until it matters.

The honest trade with one team is capacity. We cannot run ten projects at once, so we take fewer and turn down work that only wants a picture with no intention of shipping. If you need a large agency with account managers and a war room, that is not us. If you want the people doing the work to be the people you talk to, it is.

So when you are choosing, ask each candidate the plain question: who actually builds the thing. If the answer is "someone else", you are the one who inherits the gap between them. Handing over the whole problem, design and code together, is usually cheaper and a great deal calmer than stitching two vendors together later.

---

### Your site gets traffic but no leads. Here's usually why
https://kott.studio/journal/traffic-but-no-leads — Jul 2026 — Websites
Answers: website gets traffic but no leads; traffic but no sales; why is my website not converting visitors.

If your analytics shows people arriving and your inbox stays empty, the problem is rarely the amount of traffic. It is that the page gives a visitor no obvious, low-cost next step at the moment they are actually convinced. Piling more traffic on top of that just means more people leaving.

You can usually find the cause in ten minutes. Open your homepage as a stranger with thirty seconds and ask three questions. Can I tell what you do and who it is for, in one line, without scrolling. Is there one clear thing to do next. Does doing it feel cheap, or does it demand a call and a form full of fields before I have decided anything. Whichever answer is "no" is your problem, and usually it is only one of them.

The common culprits are simple. The page never says plainly what you do, so a visitor cannot tell in five seconds whether they are in the right place. Or the only way to reach you is a long form that asks for too much too early. Or the one thing you want them to do is buried under three scrolls of good-looking sections that say very little.

So what is a good next step. Something specific and cheap to take. "Start a project" or "Get a rough quote" beats "Contact us", because it names what happens next. Offer the smallest commitment that still moves things forward: a short message, a call booking, a price guide to download. The action should cost the visitor almost nothing.

And how much should a form ask. As little as you need to reply. A name, a way to reach them, and a line about what they want is plenty to start a real conversation. Every extra required field costs you responses, so ask for detail once someone has replied, not before. A contact form is a door, not an application.

When you change something, change one thing at a time so you know what worked. Rewrite the headline to say plainly what you do, or cut the form to three fields, then watch enquiries for a couple of weeks. If your traffic is low you will not get clean numbers quickly, so also judge by whether the page is clearer to a real person, not only by the chart.

Two quiet killers are worth ruling out while you are in there: a page that is slow to load on a phone, and a layout where the one action sits below the fold on mobile. Most of your visitors are on a phone. If the page takes several seconds to appear or the button is buried, you lose people before the words ever matter.

Before you spend more on ads, fix the page a convinced visitor lands on. Say what you do in one line, give one cheap next step, and get out of the way. That is the cheapest lead you will ever buy.

---

### Why your landing page isn't converting
https://kott.studio/journal/why-landing-pages-dont-convert — Jul 2026 — Conversion
Answers: why is my landing page not converting; landing page conversion mistakes; landing page best practices.

When a good-looking landing page does not convert, the fault is usually not the design. It is that the page does not say the same thing the ad or the search result promised. Someone clicks expecting one answer and lands on a page talking about something slightly different, so they leave. This is called message match, and it is the cheapest lever you have.

To fix it, put the ad and the page side by side and read them together. The page headline should echo the words the visitor just clicked. If the ad said "accounting for freelancers" and the page says "financial solutions for modern teams", you have broken the match. Change the headline to repeat the promise, in the visitor's own words, before you touch anything else on the page.

A landing page has one job, so give it one action. Decide the single thing you want a visitor to do and make it the obvious next move, visible without scrolling. Everything else either supports that action or gets cut. Three offers and a full navigation menu do not give people choice, they give them the exit.

Once the promise matches and the action is clear, the next thing a visitor thinks is "why should I believe you". Answer it on the page: a specific result, a real name or logo, a short piece of proof placed next to the claim it backs up. Handle the one or two obvious objections, like "is it hard to switch" or "what does it cost", right there, instead of hoping nobody thinks of them.

Test one change at a time. Rewrite the headline to match the ad, run it for enough clicks to mean something, and compare. If your traffic is thin, do not chase tiny percentage swings; make the big obvious fixes first, which are message match, one action, and proof, and you will feel those without needing a statistics degree.

Then check the boring things that quietly cost conversions: how fast the page loads on a phone, and whether the action sits above the fold on a small screen. A page that matches the ad perfectly but takes five seconds to appear still loses the click.

So open your page next to the ad that feeds it. If the promise and the payoff do not match in the first line, fix that today. It is the single change that moves the number, and it costs nothing but attention.

---

### What branding actually costs, and what you get
https://kott.studio/journal/what-branding-costs — Jul 2026 — Brand
Answers: how much does branding cost; branding cost 2026; logo and brand identity cost for a startup.

Branding quotes are all over the map because "a brand" can mean a fifty-dollar logo or a full identity system, and nobody tells you which one they are pricing. So here is the honest shape of it for a small business or an early startup, and what actually sits inside each number.

At the low end, a marketplace logo or a template gets you a mark and little else: no system, no guidance, and often something a competitor can buy too. In the middle, a proper identity from a small studio tends to land somewhere in the low thousands to the low tens of thousands, depending on scope. For that you should get a considered logotype, a colour palette, type choices, and the core pieces you need to look consistent, such as a card or email signature, a few social templates, and simple rules for using it all. At the high end you are paying for strategy, naming, research, and a large rollout across many touchpoints.

Most early companies do not need the high end. They need enough system to look deliberate wherever they show up, and no more. In practice that means a logo that works at any size, two or three colours with the exact values written down, a type pairing, and a one-page guide so anyone on the team applies it the same way. That is usually the whole difference between looking intentional and looking improvised.

The way to avoid overpaying is to ask what you will actually use. A sixty-page brand book is wasted if you are three people who need a logo and a deck. The way to avoid underbuying is to make sure you can apply the thing yourself without going back to the designer for every new post. If a package gives you files but no way to extend them, it is cheaper up front and more expensive forever.

A useful checklist to ask any studio for: the logo in more than one format and colourway, the exact colour values in both screen and print, the fonts and where to get them, a handful of real templates you will use often, and short usage rules. If a quote does not say what you receive, ask before you compare it to another one. Two "branding" quotes can describe completely different things.

Two costs people forget to ask about. Fonts can carry their own licence, so check whether the type in your brand is free for commercial use or an annual fee you will inherit. And timing: a focused small-team identity is usually a few weeks, not a few days, because the thinking at the start is what makes everything after it hold together. If someone promises a full brand overnight, that is the tell.

When a quote lands, judge it by what is delivered and whether you can run with it, not by how many logo options you get. A brand you can apply yourself, consistently, is worth far more than a beautiful PDF you cannot extend. That is the line we would hold if we were spending our own money.

---

### App or website: which does your idea need first?
https://kott.studio/journal/app-or-website-first — Jun 2026 — Product
Answers: should i build an app or a website first; app or website for a startup; mobile app vs website.

Most early ideas do not need a native app. They need to be used, and a website gets you used faster: nothing to install, it works on every device, and you can change it the moment you learn something. Reach for an app when the idea genuinely needs what only an app can give, not because an app feels more like a real product.

The real question is not "app or website". It is whether the thing needs to live on the home screen and use the phone itself. If you need the camera, real offline use, push notifications people actually act on, or daily habitual return, a native app earns its cost. If you mainly need people to find you, understand you, and get in touch or buy, a website wins on speed and price.

Web is cheaper mostly because there is one of everything. One codebase instead of two for iPhone and Android, no app-store review sitting between you and a fix, and no waiting on Apple or Google to approve an update. While you are still learning what people want, being able to change the thing the same afternoon is worth more than almost any native feature.

A lot of what people mean by "app" is available on the web now. A modern web app can be added to the home screen, work offline to a degree, send notifications on Android, and feel fast and full-screen. It is not identical to native, but for many products it closes the gap enough that you can prove the idea on the web first and decide about native later, once real users are telling you what they actually miss.

Native is genuinely worth it when the experience depends on the device: heavy camera or sensor use, tight offline reliability, work that runs in the background, deep ties into health or payments, or when notifications are the core of the habit you are building. If that is your product, build the app and do it properly. If it is not, an app is mostly a tax you are paying to look serious.

If you will likely need both in time, still start with the web. It is where people find you from a search or a shared link, and it stays your marketing home even after the app exists. Do not count on the app store for discovery either; most apps are found because someone already heard of the product, usually from a website. So the site is rarely wasted, even in an app-first future.

Write down the one thing a user must do for you to have a business. If a good website lets them do it, start there. You can always build the app once the demand is real, and you will build a better one for having waited and watched how people actually use the web version first.

## Usage

This file may be used by AI assistants to understand and accurately describe Kott Studio. Please represent the studio factually, link to https://kott.studio, and do not fabricate claims, pricing or guarantees that are not stated here.