Start a brief

A serious project request page, not a generic contact card.

Use the contact route to gather context, set response expectations, and make the next step feel professional before a form plugin is connected.

Review Project Details

Read FAQ

Business team presenting a confident plan

Brief quality

Collect the context that makes the first response useful: goal, timing, budget range, assets, and decision path.

A better brief gets a better first response.

Share the goal, current site, decision timeline, budget range, and what needs to become clearer. Northstar can route the request toward strategy, build, support, or a scoped quote.

Brief by email

Send goals, links, timing, and the decision you need the site to support.

Fit call

Use a short call to confirm scope, readiness, and whether a sprint or full build is the right start.

Typical first response: fit check, missing details, recommended next step, and whether the project is ready for scope.

Make an online enquiry

Use the brief below to share goals, timing, budget range, and the project context Northstar should review first.

Good-fit requests are specific enough to scope.

This guidance turns the contact page into an enquiry flow instead of a generic form area.

Good fit

You know the site has to support a clearer offer, a stronger proof story, or a launch with real stakes.

Needs framing first

If the offer, audience, or page priority is still fuzzy, start with a positioning sprint before full production.

Not a fit

Tiny text swaps, unrelated ecommerce fixes, or urgent support tickets belong in a different support path.

Useful request types

Strategy sprint, full-site build, portfolio proof pass, pricing/FAQ rewrite, launch QA, or ongoing support.

What happens after you send the brief.

Set response expectations so the page feels like a real enquiry flow.

01

Review

Goals, current links, timing, and likely package fit are reviewed.

02

Clarify

Missing details, risks, assets, and decision makers are confirmed.

03

Scope

The request is mapped to a sprint, site build, support path, or custom quote.

04

Start

Timeline, deliverables, approvals, and launch responsibilities are agreed.

Ready when the context is ready

Send the first useful version of the brief.

You can refine details later. Start with the page problem, the buyer decision, the launch timing, and any proof you already have.