To request a useful website quote, explain what the site needs to achieve, who will use it, and what those visitors must be able to do. Add the content you already have, any systems it needs to connect to, your deadline, and your budget or spending constraints.
You don't need to choose the technology or arrive with a finished page structure. You do need to distinguish requirements from ideas and mark the decisions that are still open. That gives the agency a basis for estimating the work and identifying what needs discussion first.
Describe the business need in plain language
Start with the action you want visitors to take. Requesting a service estimate, buying a product, and managing a paid account involve different work. Name the people who will use the site, including staff who will update content or handle requests behind the scenes.
List the pages or information you expect to need, even if the structure is provisional. Include every required language. Then describe the functions in terms of actions: a visitor submits an inquiry; a staff member receives it; someone responds. A short account of what should happen is more useful than a feature name whose meaning is unclear.
For each external system, record its name and the job it needs to do. Say whether information should pass from the website to that system, come back from it, or both. The agency can then investigate the connection. Naming a tool doesn't establish that the required integration is possible.
Describe the system without sharing passwords or customer records. Access can be arranged separately if the project needs it.
Show how much content is ready
Separate finished material from material that still needs work. A logo file may be ready while the service descriptions are only notes. Product photos may exist while descriptions and product details still need preparing.
Record who will write, translate, select images, and approve the final content. Mischka Studio's defined website packages assume supplied content; writing, translation, and custom integrations require separate scope. Mention those needs at the start so the quote can include the work you actually need.
| Part of the brief | A simpler requirement | An added requirement | What changes in the estimate |
|---|---|---|---|
| Pages and users | A small set of service pages for one audience | Separate information and journeys for several audiences | More structure, content, and design decisions |
| Languages | One language with final text supplied | Several languages with translation still needed | Translation responsibility, implementation, and review time |
| Content | Approved copy and usable photos | Notes that need writing and images that need sourcing | Additional content work and dependencies |
| Customer action | An inquiry form | Accounts with different permissions and paid access | More behavior to define, build, and test |
| External systems | No connection required | Data must move between the site and another service | Feasibility checks, integration work, and possible external costs |
These differences can change cost, time, or feasibility. There is no fixed uplift that applies to every project. Hosting, software, and external-system costs should also be identified separately from the website build.
Two illustrative briefs
The following examples are fictional and show how to describe requirements. They aren't Mischka Studio client stories.
A small service business
A cleaning business wants prospective customers to request an estimate. Its proposed content covers services, the area it serves, an introduction to the business, and contact details. The owner has a logo and photos but needs help turning service notes into final copy. One language is required. Inquiries should arrive by email, with no customer accounts or online payments.
That brief still leaves design choices open, but it identifies the customer action and the writing work. The owner should also state the launch constraint, budget range, and who can approve the copy and design.
A custom platform
A proposed professional directory would let members create profiles and visitors search them. An administrator would approve listings, while paid membership would control access to certain features. The business has yet to decide how payment confirmation should affect membership or what happens when access expires.
Those open rules belong in the brief. The business owner needs to decide the membership policy; the agency needs to assess how to implement it. Choosing a platform before discussing those requirements would leave a major part of the estimate unresolved.
A documented project scope
The Instrukcije Oglasnik project included search by subject, city, and teaching format, tutor accounts with profile editing, and bank-transfer subscriptions confirmed by an administrator. Its custom administration covered subjects, cities, and content. These are recorded project requirements, separate from the fictional example above. The case record doesn't establish a budget or delivery timeline.
Record what is undecided
Exact page structure, platform choice, integration feasibility, and a final budget can remain open for the first discussion. Write down each unknown, who can answer it, and what information that person needs. “Budget not set; owner needs options for the initial release” is a usable starting point. An unexplained blank gives the agency less to work with.
State any fixed launch date and why it matters. Name the person who will collect feedback and approve decisions. A deadline has to be considered alongside the scope and the availability of those decision-makers.
The editable client brief provides space to collect these answers. A completed brief is input for a discussion, not a binding quote or a booking. The written quote confirms the agreed scope, start date, and schedule.
When you're ready, use the contact form to send a summary of up to 1,000 characters. Select the relevant service and budget option; an option is available if the budget is still undecided. Keep the full brief for follow-up, because the form has no attachment field. Include the goal, main requirements, and any fixed constraint in the message.
Sources: Mischka Studio's Pricing and Web Design service information, the Instrukcije Oglasnik case study and the contact form, checked September 15, 2026.
