Skip to content
European companyFounded in 2014Built and operated in EuropePayments secured by Stripe
Gradax

The portfolio is the pitch

Websites and project systems for architecture practices, built around photography, planning stages and long decision cycles.

Sold as
One contract
Starts with
A free review

The vendors we build on, operate and resell.

  • Cisco
  • HPE
  • Dell
  • Lenovo
  • Veeam
  • WordPress
  • WooCommerce
  • Google
  • Stripe
  • Zoho
  • Atlassian

Architecture is chosen visually and then justified rationally. The portfolio does almost all of the selling, which makes photography and the way projects are presented the highest-return investment a practice can make, and the one most often left to whoever has time.

Operationally the difficulty is the length of a project. Stages, approvals, revisions and consultants stretch over months, and the practice that cannot show a client where things stand spends its evenings writing update emails.

The search side is not separate from that. "Architect" plus a city, plus project-type searches such as house extension, loft conversion or commercial fit-out. Ranking for those means the pages exist, the business is verified where it operates, and the reviews are real and recent.

How a project moves through an architecture practice

Projects run for months across stages and consultants, and the practice loses time wherever nobody can see what is waiting.

  1. Brief and fee proposal

    Fee proposals are rebuilt from a blank page for each enquiry, so a stage-based template turns a brief into a proposal in an afternoon.

  2. Design and revisions

    Revision rounds drift without a record of what the client approved, so every sign-off is logged against the drawing issue.

  3. Planning and consultants

    Waiting on the engineer or the planning officer stalls quietly, so each outstanding item shows who owns it and since when.

  4. Stage invoicing

    A stage finishes and its invoice follows weeks later, so closing the stage raises the invoice.

What people in this trade ask us

How many projects should the portfolio show?
Fewer than you think, presented better. Eight projects shown properly beat thirty shown badly, and the weakest one on the site sets the perceived standard.
Is professional photography worth the cost?
It is the single highest-return spend in this practice type. Poorly photographed good architecture reads as mediocre architecture, and there is no way to write around that.
Can clients see progress without emailing us?
Yes, and the evening hours it gives back are usually what pays for the system.
Where should we keep large drawing and model files?
On storage built for large files, with previous versions kept, rather than in somebody's personal sync folder. It should be backed up separately, so a deleted project folder can be brought back.
Can clients comment on drawings without printing them?
Yes. Comments are marked on the drawing issue inside the client area, so the feedback and the version it refers to stay together.

The infrastructure under it

Managed by the engineers who build the software, on the same contract and the same bill.

Cloud Servers

A managed server for shared project files lets large models open from the office and from site without everyone syncing gigabytes.

A server rack with glowing status lights in a data centre.

Backup & Recovery

Years of drawings and models are the practice's archive, and a single failed drive should never decide what survives.

A storage unit with a row of drive bays.

What one contract covers

  • One contract. The build, the infrastructure and the work that brings people to it, on one invoice.
  • A named team. The person on the first call stays on the project. No account managers, no handoffs.
  • Operated, not delivered. We keep it running after launch: patching, backups, monitoring and the phone when it breaks.
  • European hosting. Servers in Europe, run by us, with the data staying where you expect it to.
  • Monthly reporting. What changed, what it cost and what it produced, in language you can forward to a board.
  • No lock-in. The code, the domains and the accounts are yours. Leaving is a handover.

See what is costing you customers before you spend anything.

A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first.

  1. 01You tell us what is not working
  2. 02We review the site, the search presence and the enquiry path
  3. 03You get the three fixes worth doing, and what each is worth