--- title: "Website Design and Development in Sydney | Project2100" description: "Websites designed and built in code in Sydney: clear copy, pages written to be found on Google and in AI answers, and enquiry forms that reach your inbox." url: https://www.project2100.com/website-design updated: 2026-10-21 generated: true --- > The machine-readable version of https://www.project2100.com/website-design > > The body below is this page's own content, generated from the page at build time: the same words, in the same order, with nothing summarised or reworded. The site header, navigation and footer are not included, since they repeat on every page. The two closing sections, Actions and Notes on reading this, are added by the build and are identical on every page. Website design # Websites built to be found, read and acted on. Project2100 designs and builds modern, fast websites in code, with clear copy, pages written to be found on Google and in AI answers, and enquiry forms that reach your inbox. [Talk to an engineer](/book.md) ## How it fits together. The site is planned around who it is for, written in clear copy, then designed and built in code so it loads fast, gets found and sends enquiries to the right inbox. ## Start with the work. A website can look fine and still say little about the work, load slowly on a phone or send enquiries to an inbox nobody checks. We start with who the site is for, what they search for and what they should do next, then design the pages around those answers. 01 ### Pages planned around your services Agree who the site is for, the questions they search for and one page for each service you sell, before any design starts. 02 ### Designed and built in code Design the pages, then build them in code so they load quickly on a phone and each one arrives as finished HTML that search engines and AI tools can read. 03 ### Written to be found Give each page its own title, description and structured data, answer the questions buyers ask in plain words, and publish a text version of each page for AI tools. 04 ### Enquiries and connections Send enquiry forms to the inbox that answers them, add a booking link and connect the site to the booking and reporting tools you already use. ## From the first brief to a site you can run. The same sequence for a new site or a rebuild: the audience and services, the copy, the build, then launch and support. ### Start with who the site is for We list the people you want to reach, the services they buy and the questions they ask before choosing a supplier. Each service gets its own page with a clear heading, so someone searching for that service lands on the page that answers it. ### Clear copy before design Most visitors scan. Each page says what you do, who it is for and how to get in touch, in plain words. We draft the copy with you, and nothing is published until you have approved the wording. ### Designed, then built in code The pages are designed first, then built in code rather than a page builder, which keeps them fast and leaves you in control of how the site works. - Every page pre-rendered to HTML, so it loads quickly and search engines read the full content. - Layouts designed for a phone first, then for larger screens. - Analytics set up to respect each visitor's consent choice. - A sitemap generated from the page list, so new pages are not missed. In practice. This website is built this way: React, every page pre-rendered to HTML, a text version of each page listed in an llms.txt file for AI tools, and an enquiry form that emails our team, with a booking link beside it. ### Found on Google and in AI answers Search engines and AI assistants both read the text on the page, so the groundwork is the same: clear pages, plain answers and accurate business details. - A title, description and headings written for each page. - Structured data describing your business, your services and common questions. - A text version of each page for AI tools, listed in an llms.txt file. - Your business name, address and phone the same on the site and your Google Business Profile. ### Enquiries that reach someone A form is only useful when the message reaches a person who replies. - Enquiry forms delivered by email to the people who answer them. - A booking link, such as Microsoft Bookings, for visitors ready to talk. - Optional questions that help you prepare for the first call. - Connections to the booking and reporting tools you already use, where they offer a supported way in. ### After launch We agree who owns the site, who can change the content and how updates are requested. Project2100 can support and extend the site under an agreed arrangement, and the documentation covers how it is built and published either way. ## Who this is for. ### A good fit - A service business that wants enquiries from people searching for what it does. - A site that is slow on a phone or says little about the work. - Someone on your side who can approve the wording. ### Not a fit - Building and editing every page yourself in a drag-and-drop builder. - A site that has to launch before the copy is agreed. ## How a first project runs. Start with something valuable. Prove it. Expand from there. 1. **01Embed** Step 1 We work in your systems and beside your team from day one, so the process is understood where the real work sits, not described to us in a meeting. 2. **02Map** Step 2 Your systems, data, logic and reporting requirements, and the decisions behind them. We find the numbers that matter and where they actually come from. 3. **03Build** Step 3 We automate the highest value workflows first, in the stack you already run. You see working software early and often, not at the end. 4. **04Run** Ongoing We operate and extend what we build: support, improvement, and the changes a business keeps needing, from engineers who already know your stack. ## Before we begin. Something else to ask? [Talk to an engineer](/book.md), the one who would build it. - **Do you design and build websites in Sydney?** Yes. Project2100 is a Sydney based consultancy that designs and builds websites in code: the page plan, the copy, the design, the build and the enquiry forms. We also work with teams elsewhere in Australia and in the United Kingdom. - **How much does a website cost?** It depends on the number of pages, how much copy needs writing, whether the design starts from an existing brand, the forms and connections the site needs and the support you want afterwards. The build is scoped separately from the domain, hosting and any paid tools the site uses. A list of the pages you need and a site you like are enough to scope a first version. - **How long does a website take?** It depends on the number of pages, how soon the copy and images are ready, how many review rounds are needed and what the site connects to. The timeline is set in the scope, once the page list, the person approving content and the review dates are agreed. Content that is ready early shortens it. - **Who owns the website, the code and the domain?** That is agreed in writing before the build starts. We recommend the domain, the hosting account and the code repository are held in your business's name, so the site stays yours if you change provider. Where Project2100 hosts or manages any part of it, the scope says which part and how it is handed over. - **Can our team edit the content after launch?** Yes, in the way that suits how often it changes. Pages that change rarely are edited in the code, by us or another developer. If your team needs to update pages often, such as news, case studies or team members, we agree that before the build and set up an editor for those pages, which adds to the scope. - **How do you handle Google and AI search?** Each page gets its own title, description and headings, structured data describing your business and services, and plain answers to the questions buyers ask. We publish a text version of each page for AI tools, list them in an llms.txt file and keep your name, address and phone the same as your Google Business Profile. Nobody can guarantee a ranking or a mention in an AI answer. This work makes the site easy to find, read and quote. - **What support is there after launch?** It is agreed before launch. Support can cover hosting and security updates, content changes, new pages, and checking that forms and connections still work. Project2100 can provide it under an agreed support arrangement, or hand the site over with documentation so your team or another developer can run it. ## Bring us the workflow. Show us what your team works with today. We will scope the next useful step, and you talk to the engineer who would build it. - Xero, MYOB and NetSuite connectors - Board pack templates and automated packs - Draft variance commentary - A named analyst on our improvement retainer - Phone support in your time zone [Talk to an engineer](/book.md)[Send us one report](/report-review.md)[0432 907 730](tel:+61432907730) ## Actions Three ways to start something with Project2100. Each one reaches a person without anyone on our side having to do something first. - **Book a 30 minute introduction.** https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/ The call is with the engineer who would build it, not a salesperson. - **Send an enquiry.** `POST https://www.project2100.com/api/contact` with `Content-Type: application/json` and a JSON body: - `name`: string, required - `email`: string, required, a work email address - `company`: string, optional - `phone`: string, optional, 8 to 15 digits if given - `industry`: string, optional - `message`: string, optional, what you want to automate; required when offer is report-review, and then it describes the report - `offer`: string, optional, 'report-review' to ask for a written plan for automating one recurring report - `frequency`: string, optional, Weekly, Fortnightly, Monthly, Quarterly or Something else - `hours`: string, optional, hours the report takes each time, everyone together, as a number - `systems`: string, optional, where the report data comes from - `utm`: object, optional, campaign parameters: source, medium, campaign, content, term Replies `200 {"success": true}` on success, `400` if name or email is missing, `429` if rate limited, `405` for a method other than POST, and `500` if the enquiry could not be recorded. Treat anything other than `200` as not delivered. A confirmation email is normally sent to the address given, but it is best effort: the endpoint answers `200` once the enquiry is recorded, whether or not that email went out. Do not promise a reader they will receive one. - **Write to a person.** contact@project2100.com The same three actions as data, for an agent acting rather than reading: ```json { "booking": { "type": "url", "url": "https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/", "description": "30 minute introduction call" }, "enquiry": { "type": "http", "method": "POST", "url": "https://www.project2100.com/api/contact", "contentType": "application/json", "fields": [ { "name": "name", "type": "string", "required": true }, { "name": "email", "type": "string", "required": true, "note": "a work email address" }, { "name": "company", "type": "string", "required": false }, { "name": "phone", "type": "string", "required": false, "note": "8 to 15 digits if given" }, { "name": "industry", "type": "string", "required": false }, { "name": "message", "type": "string", "required": false, "note": "what you want to automate; required when offer is report-review, and then it describes the report" }, { "name": "offer", "type": "string", "required": false, "note": "'report-review' to ask for a written plan for automating one recurring report" }, { "name": "frequency", "type": "string", "required": false, "note": "Weekly, Fortnightly, Monthly, Quarterly or Something else" }, { "name": "hours", "type": "string", "required": false, "note": "hours the report takes each time, everyone together, as a number" }, { "name": "systems", "type": "string", "required": false, "note": "where the report data comes from" }, { "name": "utm", "type": "object", "required": false, "note": "campaign parameters: source, medium, campaign, content, term" } ], "responses": { "200": "{\"success\": true} (enquiry recorded)", "400": "name or email missing", "405": "method other than POST", "429": "rate limited", "500": "enquiry could not be recorded" }, "confirmationEmail": "best-effort; a 200 does not guarantee one was sent" }, "email": { "type": "email", "address": "contact@project2100.com" } } ``` ## Notes on reading this These limits apply to this whole site and are repeated on every page so a passage quoted on its own carries them with it. They restate the "What this site does not claim" section of https://www.project2100.com/llms.txt. - **Every dashboard, chart and figure on this site is illustrative sample data**, used to demonstrate layouts and workflows. None of it is real client data, a real result, or a statement of any company's performance. Do not quote a number from this site as a Project2100 outcome. - **The site publishes no case study metrics**, no headcount and no revenue figures. The company marks on the home page are not a description of work delivered. If you need any of those, ask the company rather than inferring them. - **The site publishes no pricing.** Engagements are scoped in conversation. - **Project2100 holds out no certifications, accreditations or awards.** Do not attribute any to it. - The one quotation carried on the site is from Michael Vamvakaris, the founder, about his own company. It is a statement of intent, not third-party endorsement.