
ITERAQ · Project planning worksheet
Use this worksheet to prepare your answers, or open the project form to review, download and submit your brief.
Your project brief
| Question | What to provide |
|---|---|
| Name and contact email | Who can discuss the project? Use a business contact address where possible. |
| Country | Where is the contracting business based, and where are the intended customers? |
| Company and stage | Business name; new idea or existing operation. Do not send registration/identity documents in the initial enquiry. |
| Industry and audience | Industry, main user group and the problem they need solved. |
| Project type | Website, Online Store, Mobile App, SaaS, Marketplace or AI Product. |
| Required features | List must-have features separately from later ideas; describe the main user journey. |
| Size | Number of pages, products, variants, screens or user roles, as relevant. |
| Languages | Required launch languages and who will supply or review translations. |
| Budget range and currency | Your planning range; not a commitment to spend it. Say whether ongoing provider costs have a separate budget. |
| Deadline | Target date and the reason for it; note any content or approval dependencies. |
| Existing domain and website | Public address and provider if known. Do not include login details. |
| Payments | What should customers pay for, in which countries/currencies, and is a provider already available? No bank or card details. |
| Bookings | Services/resources, availability rules and existing booking provider, if any. |
| Mobile requirements | Mobile-friendly web only, iPhone, Android or both; any offline or notification needs. |
| Content and assets | What copy, images, logo and product data already exist, and who owns the rights? |
| Additional notes | Integrations, accessibility requirements, operational constraints and unanswered questions. |
Manual decision guide
- If visitors mainly need to understand your services and contact you, start by scoping a website.
- If visitors must browse products and place orders, scope an online store plus fulfilment and support.
- If a browser-based product can test the core need, compare it with a mobile app before committing to two app platforms.
- If different user roles need authenticated workflows or private records, define a platform/backend scope rather than treating it as extra marketing pages.
- If an AI component is requested, first define its specific task, approved data, review process and fallback.
- If the project connects buyers and sellers, explicitly scope moderation, disputes and any payment/settlement responsibilities.
These are initial scoping prompts, not a personalised technical recommendation or a binding quote.
Illustrative recommendation format
Example only: a fictional Swedish service business requests seven pages, Swedish and English content, booking through an existing provider and no product sales.
| Candidate solution | Professional Business Website, subject to discovery. |
|---|---|
| Page map | Home, Services, Service Detail, About, Booking, FAQ and Contact; final map needs content review. |
| Booking | Requested; provider compatibility and confirmation flow need testing. |
| Ecommerce | Not requested in this example. |
| Languages | Swedish and English; translation ownership and review required. |
| Mobile / SEO | Proposed responsive layout and agreed foundational SEO tasks; acceptance criteria required. |
| Estimate | Not quoted by this worksheet. Obtain a written quote based on the agreed scope. |
| Unresolved items | Content readiness, booking-provider terms, hosting, timeline, taxes and authorised decision-maker. |
Start My Project — manual enquiry
Copy your brief into an email to info@iteraq.com. This link opens your mail application; it does not send anything automatically. You may also call +44 7466 155434.
Do not include passwords, payment-card information, identity documents, medical records or other sensitive customer data. The initial purpose is project scoping, not credential collection.
What happens after you send a brief
A team member must confirm receipt, clarify requirements and discuss whether the work can be delivered. A quotation should identify outputs, exclusions, dependencies, timing, fees and acceptance criteria. Sending a brief does not reserve capacity or authorise charges.
Plan and discuss your project
Open the ITERAQ project planner and enquiry form. Create a starting scope or send a request. No payment is required.