Most agency sites have a page about their process. Five circles, words like ‘discovery’ and ‘ideation’, an arrow pointing from left to right. What actually happens between ‘we had a good chat’ and ‘we can start’ usually stays vague. With us, that’s two to three weeks, sometimes one for a small site, and below is what happens in those weeks. In plain English, with dates, deliverables and the moments where you decide. Whether you’re considering a platform or just wondering if we fit.

Mistakes that rarely show up in a quote. You only notice them three months later when you hit something nobody had discussed, or when the scope conversation starts to sour the whole working relationship.

Studio Ubique has been working since 2012. We deliberately run the same process on every project, even though nobody at the first call knows what'll end up live. The step plan works the same for a small WordPress build as for a platform with API integrations and custom user flows. What happens in each phase differs, the steps don't.
01
Thirty to forty-five minutes, via Google Meet. One of us covers the sales and project side: where you stand now, what you want to achieve, what deadline is in your head. The other covers tech: stack choices, integrations, what’s feasible in the time and budget you mention. No sales cycle of three meetings before the first real question gets asked. By the end of this call we know if this is worth a proposal, or whether we can be honest about fit. Often you send us some extra input after the call. We take it into the research.
02
What happens between the call and the proposal differs by project. For a platform our tech lead, together with the development team, drafts a technical scope with integrations, data model and risk areas. For a marketing question a strategic document goes on the table, with market, audience and hypotheses. For a rebuild of an existing site we do an audit, with technical and content findings. Lead time: five to ten working days. We present the plan in a second call. Then we send you the document, so you can read it in your own time and respond to the thinking before the price is attached. In that call we book the next one straight away.
03
In a third call we go through the proposal together: the price, the planning, the details of the terms and optional services, and whether it fits you. We write the proposal in our own CRM. It always contains three things: the price, the scope and a section ‘what’s not included’, because without it every scope discussion turns into ‘but I expected that too’. In the investment overview you tick what you do and don’t want to take on. Questions go through email or a quick call, not through a forced form. You sign digitally for approval, and that starts the next phase.
04
One hour, just before the actual start. We sort out access (CMS, hosting, design tools), confirm a fixed point of contact on both sides, and walk through the planning for the first two weeks. No welcome package or celebratory moment. We do hand over a document with all agreements in it, where they weren’t already in the proposal.
05
We work in short cycles, with weekly calls of thirty minutes. Feedback per round via Figma, email or a (video) call. Each design or page includes three feedback rounds, unless the proposal says otherwise. We test on a staging environment, and launch happens only after your explicit approval. After that we stay available for support after launch. If you want ongoing maintenance, that’s covered by our website support.
From the University of Twente and Creditsafe to Sokkies, FlevoDirect and AGN, and through an agency KPN, Wortell and Ziggo as well. And a few hundred companies you’ve probably never heard of, but who got properly looked after all the same. That, on reflection, is the whole story.
Studio Ubique has worked since 2012 with companies that don’t have the time to get to know an agency through three months of misses. We’ve seen the same missteps often enough to know where they start: at the front, in a first call where too little gets put on the table, or in a proposal that was written too quickly.
The questions that come up most often, answered here. Yours not among them? Just ask, there's a human on the other end.
A first call costs nothing. Thirty to forty-five minutes via Google Meet, with two people from our side at the table (one for sales and project, one for tech), so you don’t have to wait for a separate technical conversation to find out if something is feasible.
By the end of the call we know whether this is worth a proposal, or whether we can be honest about fit. No deposit, no commitment, no sales cycle of three meetings before the first real question gets asked.
Two to three weeks, sometimes one for a small site. Those weeks hold three conversations: the first call, a call where we present the plan, and a call where we go through the proposal. The research document alone takes five to ten working days, depending on what the project needs. For a platform our tech lead writes a technical scope with integrations, data model and risk areas. For a marketing question a strategic document with market, audience and hypotheses. For a rebuild of an existing site an audit with technical and content findings.
We present the document in a second call and send it to you afterwards, so you can respond to the thinking on substance before a price gets attached. No proposal goes out Friday afternoon after a first call, because a defensible proposal takes research, not half an afternoon of template filling.
Nothing happens. The first call and the proposal are free. For some projects that need research or a strategy document up front, we agree a separate fee beforehand, confirmed by email, so it never turns up on an invoice as a surprise. You keep the document and the proposal. We’ve had useful conversations land at “this isn’t the right moment” or “we’d rather work with someone closer to home”, and that’s also a fine outcome.
What we don’t do: chase you with follow-up emails for three months, or send a watered-down second proposal with a discount attached. If the answer is no, the answer is no, and you can come back when something changes.
A fixed price per project. For larger or open-ended projects we work on an hourly basis, with a budget up front. The proposal lists what’s in scope and what isn’t, and quotes a fixed price for the scope. New requests that come up during the project (additions, changes outside the agreed scope) get quoted separately at our standard rate of €60-€65 per hour, with the classification (correction versus new request) confirmed in writing before the work runs.
For ongoing work after launch we offer website support packages with monthly hours and response times, or a dedicated-developer retainer with a fixed monthly capacity. Both are time-and-materials shapes with predictable monthly cost.
Scope changes get classified before any work runs. A correction (where the delivered work doesn’t match the approved design or written specification) gets fixed without extra cost. A new request (anything outside the approved scope: changes to layout, typography, spacing, responsive behaviour, interactions, functionality or content structure not in the approved materials) gets quoted as additional work and counts against the three revision rounds included in the proposal.
Requests beyond the three included revisions get quoted separately at €60-€65 per hour. We confirm the classification in writing before doing the work, so you know whether something falls inside or outside the original scope before time gets billed. That’s exactly the conversation that derails most agency projects, which is why we’d rather have it explicitly than implicitly.
Depends on the project type. For a platform build you get a technical scope document with integrations, data model, third-party dependencies and risk areas. For a marketing question (SEO, paid, conversion) you get a strategic document with market analysis, audience hypotheses and proposed approach. For a rebuild of an existing site you get an audit with technical findings, content findings and prioritisation.
The document is the substance of the conversation. The proposal that follows is the commercial wrapper around it (price, deliverables, planning, terms). We present the document in a second call and send it to you afterwards, so you can respond to the substance before a price turns the discussion into a negotiation.
At the first call: two people from our side, one for sales and project, one for tech. After approval: a fixed team for the duration of the project, with overlap between sales, design and development. One point of contact on your side, one on ours, but the team isn’t dependent on a single person. If someone is out sick, the work continues.
For larger projects we agree on a RACI structure in onboarding (who’s responsible, who approves, who’s consulted, who’s informed) so internal stakeholders on your side don’t surprise the work two weeks before launch. We map dependencies on your team early (IT for hosting access, legal for cookie consent text, marketing for content) so those don’t become last-minute blockers.
Almost always, but only after we’ve looked into it. You have the final say, it’s your business. We check what it takes first, then tell you plainly what’s possible, what isn’t and what it costs, with the reason behind it. That’s what you hire us for, not a nod. And a site that moves your business forward is the only way we’re still working together five years from now.

Contact
Not everyone likes to write. Rather talk to someone first? Book a 30 to 45 minute intro call through Calendly. It's free, and by the end you'll know whether a proposal makes sense.
Book a first call(opens in a new tab)Tell us what's stuck, what you want to build, or what needs fixing. You talk to someone from sales and someone technical, and we reply within one working day. First a conversation, then a plan, only then a price.