Based in Kyiv

©2026

What a Proposal From Arche Actually Looks Like

A brass balance scale with wooden blocks and a folded sheet

Clients almost never ask how we arrived at a price. They should. This is the arithmetic we do before sending a number, and why we stopped billing by the day two years ago.

In early 2022 we quoted a project in days. Fourteen days of design, nine of build, a day for copy support. The client signed, we started, and by week three the day count had quietly become nineteen and twelve. Nobody had done anything wrong. The brief had just grown the way briefs grow, one reasonable request at a time. We finished the project, ate the overage, and sat down afterward to figure out why it kept happening.

Why Days Stopped Working

A day rate feels honest because it looks transparent. Ten days at 450 USD is 4,500 USD, and anyone can check the arithmetic. The problem is that a day rate puts the client in charge of a variable neither of us can actually control well: scope creep measured in hours. Every extra round of feedback, every “could we also see it with the logo bigger,” quietly taxes the budget, and someone has to be the one to say stop. That someone was usually us, and we are bad at it.

The Trust Problem

Day rates also create a strange incentive. If we work fast and the client is happy in six days instead of ten, we’ve effectively been paid less for a better outcome. Clients notice this, even if they don’t say it, and some start to wonder whether slower work is being manufactured. We never did that. But the structure invites the suspicion, and that’s reason enough to drop it.

A blank document with a binder clip, a fountain pen and glasses
The day count kept growing, so the proposal stopped counting days.

How We Price Now

Since autumn 2022 every proposal from Arche is a fixed fee attached to a fixed, written scope. Not a scope in spirit, an itemized one: number of templates, number of revision rounds, what’s included in “content strategy” and what isn’t. The fee is the same whether we finish in nine days or fourteen, and that symmetry matters more than the number itself.

What Goes Into the Number

We build the estimate from four inputs, roughly in this order:

  • Template count and complexity, not page count. A pricing page with a comparison table is heavier than five identical content pages.
  • Content readiness. If a client has no copy yet, we add a content workshop or writing budget rather than guessing.
  • Integration surface. Payment, booking, CMS, email, each one is a line with its own estimate, because each one can go sideways independently.
  • Revision structure. Two structured rounds, not “unlimited revisions within reason,” because reason is exactly what gets argued about at hour forty.

We price the first three against a rate card we keep internal, around 7,800 to 14,000 USD for a marketing site of eight to twelve templates, depending on how custom the interaction work is. A five-page studio site with a contact form sits near the bottom. A product site with a configurator and Stripe integration sits well above it.

What a Proposal Document Contains

Clients sometimes expect a proposal to be a single number in an email. Ours runs four to six pages, and we send it as a PDF with a short cover note, never just a figure pasted into a message.

The Sections We Always Include

Every proposal from Arche has the same backbone: a one-paragraph restatement of the problem, so the client can confirm we understood the brief before anything else; a scope table listing every deliverable by name; an explicit list of what is not included, which is often the section people read most carefully; a timeline broken into milestones with payment tied to each one; and a short paragraph on what happens if scope changes mid-project, including our hourly rate for anything outside the original list, which currently sits at 95 USD.

We learned to write the exclusions list the hard way. A 2023 proposal for a nonprofit in Lviv didn’t mention that we weren’t providing translated copy for the Ukrainian version of the site. The client assumed it was bundled. We ended up doing it anyway, unpaid, because arguing about it felt worse than the hours it cost. Now every proposal has a line that says, in plain words, what we are not doing.

A good proposal is less a sales document than a contract with the ambiguity removed in advance.

Milestones and Payment

We split payment into three parts: 40 percent on signing, 30 percent at design approval, 30 percent at launch. The first payment is non-negotiable and it’s not really about cash flow, though it helps. It’s a filter. A client who hesitates to commit 40 percent upfront is usually a client who hasn’t fully committed to the project internally either, and that uncertainty shows up later as indecision on colors, copy, and launch dates.

Handling Scope Changes Honestly

Changes happen on almost every project, and we don’t treat that as a failure of planning. When a client asks for something outside the signed scope, we write a short change order, one paragraph describing the addition and its cost, and we wait for a yes before touching it. It takes ten minutes and it has saved us from at least a dozen arguments about what was “basically included.”

Why Fixed Fees Make Us Better, Not Just Safer

The surprising effect of switching to fixed fees wasn’t financial discipline, though we got some of that too. It was that estimating forced us to actually think through a project before starting it, instead of discovering its shape as we went. Projects we scope carefully tend to need fewer revision rounds, because we’ve already had the hard conversations about what the client actually wants before any screen exists.

We still get pricing wrong sometimes. A travel booking site we quoted at 11,500 USD last spring needed almost twice the integration work we estimated, because the client’s reservation system turned out to have an undocumented API. We ate the difference, updated our internal notes, and now ask a more specific question during discovery calls: can you show us your booking system’s documentation before we quote. Every miss becomes a question we ask earlier next time.

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent posts