Loading...
Loading...
New homes scheme website
One site for one scheme. The place, the house types, the site plan and the register form, scoped around your launch date.
Three routes
The right route is the smallest one that respects your published hour. I mark the standalone site because it needs nothing from your corporate site. Send the launch date first. If a route is too close to that date, I say so and name the smaller one.
You run a corporate site your team already edits. I add the scheme section, the house types, the site plan and the register form. An agency that controls that site becomes a risk to your launch date. Send me the platform your corporate site runs on first. If it is one I do not take, I say so and name the standalone route.
Scoped in writing after the inventory.
One scheme, one address, the one printed on the hoarding, the brochure and the portal listing. The story, the house types, the site plan, the phases and the register form, and nothing else. The scheme site never touches your corporate site.
Scoped in writing after the inventory.
You launch several schemes. Each new site reuses the approved structure, the house-type pattern and the phase controls. Each one still gets its own inventory and its own written scope. The first site takes longer than a single-scheme site, because you agree the pattern as well as build it.
Scoped in writing after the inventory.
Who does the work
Scope
The process
The inventory comes first. The written scope then names the launch date you supplied, the approval points and the accepted asset list. Work starts after you approve them.
I list the house types, plans, specifications, images, documents and form fields. We agree the launch date and hour, the named approver, and where each lead goes.
Output: A page map, an asset list, the lead route, the missing items and my route recommendation.
I build the story pages, the house-type pages and the site plan on a private staging site. I add the phase controls and the register form. I wire the form to the CRM and test it end to end. You check every plan, specification, BER number and PSRA number.
Output: A complete staging site, a tested lead route, a load check and an acceptance checklist.
I publish after your named approver releases the scheme. I check the live pages and hand over the editor guide. Cover across the launch weekend is a separate item, agreed in the written scope.
Output: A live scheme site, an editor guide for the phase releases, a rollback point and the agreed end state.
Safeguards
Three things carry the risk here. A published hour that cannot move. A lead route you do not control. Claims that your advisor and your agent own. Here is what controls each one.
Questions
Send the date, the hour and the assets first. I reply in writing after the inventory. I scope the plan around your date, and the inventory names the missing items and the date risk.
Yes. The price list, the phase state and the unit status are fields your team edits. That control is an acceptance test in the written scope. An edit goes live with no rebuild wait, and the scope names the time it must meet. Late prices are normal, so the build assumes them. Content sits in fields, not in artwork, and we agree the cut-off at the inventory.
The form posts to your agent's CRM endpoint, with a field mapping we agree in the inventory. Where there is no endpoint, it posts to a named inbox. I test either route before launch week, and the written scope names the test date. I publish every PSRA registration number and every privacy link you supply. The consent text names every party the lead reaches. Your agents and your advisor confirm the wording, and I publish it as given.
The pages are pre-built, so a page view does not wait on a database. A load check runs before launch, and the scope names the threshold it must meet. I timestamp every registration. You can close the form, cap it, or turn it into a waiting list. Your agent decides who to contact, and in what order. The site does not allocate units and does not tell a buyer their position.
No. The site links the official sources and gives no scheme advice. Scheme rules and price ceilings change, so your advisor and your agent answer buyer questions.
I take a published launch hour only when the written scope names a second web developer. That person has access and has run the release steps. If no cover is available, I tell you before you commit, and I do not take the hour.
You get a written scope with a payment schedule and my company details, in the format your finance team needs. I invoice against that schedule, not against hours. I send the supplier documents your procurement team asks for. We agree anything outside the scope in writing before it starts.
You own the domain, the content, the code and the leads throughout. We agree the end state before launch: archive the site, or redirect it to your corporate development page. I inventory and scope a next phase with new house types as new work.
Send the launch date and hour, the house-type schedule and the site plan. Tell me which agent takes the leads. I return the route, the risks and the decision points in writing.
Send me your launch date