Starting a new website or app is exciting—but a bit of preparation goes a long way. Having the right things ready before development begins saves time, keeps costs predictable, and helps your team deliver exactly what you need. Here’s a practical checklist of what to prepare.
1. A clear brief (goals and scope)
What it is: A short document that answers: What is this project for? Who is it for? What should it do (and not do)?
Why it helps: A clear brief keeps everyone aligned. It avoids “we thought you meant something else” and scope creep. You don’t need a formal document—a few bullet points or a short description is enough to start.
Include: Main goal (e.g. get more leads, sell products online, let customers book appointments). Who will use it (customers, staff, both). Must-have features vs nice-to-haves. Any systems it should work with (email, CRM, payment gateway).
2. Content (text and structure)
What it is: The actual copy and how the site or app is organized: page names, menu structure, key messages.
Why it helps: Content drives design and build. “We’ll add the text later” often leads to placeholder layouts, rework, and delays. You don’t need every word final—but you do need a clear structure and draft copy for the main sections.
Prepare: Homepage headline and short intro. Main pages or sections (e.g. About, Services, Contact; or for an app: main screens and actions). Contact details, address, and any legal or policy pages you know you’ll need. If copy isn’t ready yet, at least list what goes where.
3. Assets (images, logo, brand)
What it is: Logo, brand colors (or guidelines), and any images or media you want to use.
Why it helps: Design and layout depend on real assets. Generic placeholders lead to rework when you replace them later. Even a simple logo and one or two key images help the project look and feel right from the start.
Prepare: Logo in a high-quality format (e.g. SVG or PNG). Brand colors (hex codes or “use our existing site”). Key images: team, product, or hero images in correct size and format. If you don’t have professional photos yet, say so—your team can suggest stock or simple solutions.
4. Access and accounts
What it is: Everything your developer needs to connect, host, or manage the project.
Why it helps: Waiting for login details or domain access can block progress. Having these ready (or planned) keeps the timeline on track.
Prepare as relevant: Domain (where it’s registered and how your developer can point it to the new site). Hosting (access if you have it, or a new account). Third-party services (payment gateway, email provider, analytics) and who will create or share accounts. Your developer can tell you exactly what they need.
5. A realistic timeline
What it is: When you need to launch (or the first version) and any hard dates (event, campaign, contract).
Why it helps: Development takes time. A realistic timeline allows for design, build, content, and testing. Rushed projects often cost more and deliver less. Sharing your target date and constraints early helps the team propose a plan that works.
Discuss: Ideal launch date and “must launch by” date if different. Any phases (e.g. MVP first, then add features). Who on your side will review and respond so feedback doesn’t delay the project.
Summary
Before you start a website or app, prepare: (1) Brief — goals, audience, must-haves, integrations. (2) Content — structure and draft copy for main pages or screens. (3) Assets — logo, colors, key images in good quality. (4) Access — domain, hosting, and key accounts your developer needs. (5) Timeline — target date and who will review and approve.
You don’t need everything perfect on day one. You do need enough clarity and materials so the project can move forward without big surprises. If you’re not sure what’s enough, ask your developer for a short “what we need from you” list.
Ready to start? Get in touch with your goals and we’ll help you turn them into a clear plan and a realistic timeline.