Skip to main contentLaunch offer: 10% off your first order of any service Browse services
Hylance
Programming4 min read

Before You Hire a Developer: Prepare This One Page

A simple one-page brief helps you define the goal, pages, features, content, and accounts before hiring a developer.

By the Hylance editorial team · Updated

Before You Hire a Developer: Prepare This One Page

Key takeaways

  • Before asking for any quote, write a one-page brief: the website goal, page list, and features.
  • Split features into must-have for launch and can-wait items; this lowers cost and speeds up launch.
  • Register the domain, hosting, and payment gateway in your name, and give the developer temporary access.
  • Break the project into stages, and review and test each one before confirming delivery.

When a business owner says, "I want a website like that company’s site," every developer understands something different. The result is widely different quotes, delayed delivery dates, and endless revision rounds. The fix is simple: before you ask for any quote, write one page that answers the following questions.

1. What should the website achieve?

Write the goal in one sentence: sell products, collect booking requests, introduce customers to your business and send them to WhatsApp, or showcase your work. The goal determines everything after that, from the number of pages to the type of admin panel you need.

2. List of pages and features

List the pages by name (Home, About Us, Products, Product Page, Cart, Contact Us...), then divide features into two groups:

  • Must-have for launch: what the website cannot work without, such as online payment or a booking form.
  • Can wait: such as a blog, loyalty program, or multiple languages.

This split alone can reduce cost and speed up launch, because the developer prices what you need now, not what you might need someday.

3. Examples you like, and why

Add two or three links to websites you like, and next to each one write exactly what you like about it: the product page layout, the ease of checkout, or the colors. Saying "I like it" is not enough. The goal is not to copy someone else’s website, but to make your taste clear.

4. Who will prepare the content?

Text, product photos, and the logo are some of the biggest reasons website projects get delayed. Be clear about who will write the copy, who will photograph the products, and when everything will be ready. If you will deliver it later, agree that the developer will build with placeholder content first, then replace it.

5. The accounts should be in your name

  • The domain is registered in your name and on your email.
  • The hosting or platform account (such as Salla, Zid, or WordPress) is yours, and you pay its bills yourself.
  • The payment gateway and shipping company accounts are under your business name.
  • The developer gets temporary access, and you change it after delivery.

That way, your website does not become dependent on any third party if the working relationship ends.

6. Questions to ask before you agree

  • What technology or platform will you use, and why is it a good fit for my project?
  • Will I receive the source code or export file, and who owns it?
  • How many revision rounds are included, and what counts as extra work?
  • Will you show me how to use the admin panel so I can add products and edit text myself?
  • Who is responsible for backups and updates after delivery?

7. Break the project into stages

Instead of one large payment, split the work into stages that you review and test one by one: design, then the core pages, then payment and shipping, then launch. At each handoff, test the website on your phone, fill out the forms yourself, and place a trial order. On Hylance, the amount for each order stays held by the platform until you confirm that you received what was agreed, so make the description of each stage clear enough that you know exactly when to approve it.

Example: a one-page brief for a small store

Let’s say it is a store selling specialty coffee in Riyadh. The brief could look like this: Goal: sell products with online payment and delivery inside Saudi Arabia. Pages: Home, Products, Product Page, Cart and Checkout, Return Policy, Contact Us. Must-have for launch: mada and Apple Pay, one shipping company integration, and discount coupons. Can wait: the blog, loyalty program, and English version. Content: 30 products with photos and descriptions, to be delivered within two weeks. Accounts: the domain, platform, and payment gateway are all registered under the establishment’s name.

This paragraph alone is enough for any developer to give you an accurate quote, and it lets you compare offers on the same basis.

Mistakes that delay the project and increase the cost

  • Asking for "all the features" from day one. Every extra feature needs design, testing, and maintenance.
  • Changing the requirements after work starts without adjusting the timeline and price. Agree from the start on how any additions will be handled.
  • Delaying the content delivery, then expecting the developer to keep the original deadline.
  • Testing the website only on a computer, even though most visitors browse on mobile.
  • Relying on a verbal agreement only. Everything agreed on should be written in the order description or in the platform chat.

What should you receive at final delivery?

  • Login details for the admin panel with owner-level access.
  • The source files or export file if the website was custom-built.
  • A recorded or written explanation of how to add products and edit text.
  • A list of the subscriptions you will pay for yourself and their renewal dates: domain, hosting, and paid plugins.

Keep the one-page brief after launch

The brief is still useful after the website is delivered. You will come back to it when you make your first improvement, so you can see what was postponed and why. It also becomes the starting point for any developer who continues the work after the first one. Update it whenever you add a feature or change an account, so you always have a complete picture of your website that no one else has except you.

Website and online store services on Hylance

Frequently asked questions

What should I prepare before asking a developer for a website?

Prepare a one-page brief that explains the website goal in one sentence, the list of pages and features, examples you like and why, who will prepare the content, and which accounts the website will be built on.

Whose name should the website accounts be under?

They should be under your name: the domain on your email, the hosting or platform on your account, and the payment gateway and shipping company under your business name. The developer should get temporary access that you change after delivery.

What questions should I ask a developer before agreeing?

Ask which technology or platform they will use and why it fits your project, whether you will receive the source code and who owns it, how many revision rounds are included, whether they will show you how to use the admin panel, and who is responsible for backups and updates after delivery.

Ready to put this into practice?

Browse Programming & Tech services on Hylance and order what your business needs, with escrow that protects both sides. Or create an account and list your first service in minutes.

All Programming guides