Mason Hills Digital
The site for an Austin software company that builds operations systems for print shops, bakeries and factory floors, and runs a marketing arm alongside.
What they came with
A software company and a creative agency sit under one roof, and most visitors arrive wanting one of them without knowing the other exists. The operations buyer running a print shop and the owner after a brand refresh want different proof, different language and a different next step, but they land on the same home page. The enquiry that comes back then has to say which arm it belongs to before anyone can pick it up. None of that can be solved by adding pages, because the whole site is four of them and both arms have to stay visible from the top.
What the build had to do
One home page, two audiences
The home page has to introduce operations software and creative marketing without either reading as the afterthought. Each arm gets its own full-width statement, its own image and its own route out, sequenced so a visitor can stop at whichever one they came for.
Capability tiles as the catalogue
The software arm has no shipping product to photograph, so five capability areas stand in for it: job and project tracking, reporting and insights, sales and customer management, inventory and supply chain, and scheduling and production planning. The grid has to do the work a screenshot would normally do, which puts the whole weight on the tile headings and the two-line descriptions under them.
An enquiry that sorts itself
The consultation form takes name, email and phone, then asks which arm the visitor wants as three named options rather than free text, then how they heard about the company from a fixed list, then the message. The enquiry therefore arrives already classified, so triage is a read rather than a decision.
Display type at hero scale
A heavy display face carries the headlines against a lighter grotesque for body copy. It has to hold across a full-bleed photograph at hero size and still stay readable when the same face drops into a two-line tile heading in the services grid.
List capture and account plumbing
A mailing-list block sits at the foot of every page, and Squarespace's customer-accounts bundle and cart route are provisioned on the template. That leaves a path to selling packaged work later without recutting the header or the checkout route.
Technical detail
Sections as the layout contract
7.1 renders a page as a stack of typed sections, each holding blocks from a fixed vocabulary, with layout coming from Fluid Engine grid configuration rather than a template file. The build therefore expresses its own rhythm inside that vocabulary, which keeps day-to-day editing in the client's hands and trades away arbitrary one-off layout.
The form is the only write path
Everything else on the site is read-only, so the consultation form is the whole integration boundary and its two enumerated fields are effectively the schema. If service interest and source were free text, every enquiry would need a person to classify it before routing; as fixed options they can drive assignment directly.
Cached documents, invisible bot check
HTML is served from Squarespace's CDN with a long edge age, so the document a visitor receives is a cached artefact and the only per-request work is the form endpoint. The form block declares captchaEnabled with a reCAPTCHA Enterprise site key injected on every page that carries a form, which keeps the short field list free of a challenge step at the cost of a third-party script sitewide.
The stack
Platform
Front end
Services
- Sector
- Software and marketing services
- Audience
- Print, bakery, factory operators
- Shape
- Dual-arm services site
- Platform
- Squarespace 7
Something like this to build?
Tell us what runs today and where it hurts. An engineer reads it and replies.