Strategy, design & growth
Creative & growth engineering
Marketing sites, landing pages, documentation and the measurement behind them — engineered rather than assembled, so they load fast, rank, and can be changed without a ticket.
- Marketing sites
- Landing pages & experiments
- Technical SEO
- Documentation sites
- Analytics & attribution
- Content pipelines
What we build
- Marketing sites
- Static, fast and accessible, with a content model your team can edit.
- Landing pages and experiments
- Variants that can be shipped and measured without an engineering cycle.
- Technical SEO foundations
- Structured data, sitemaps, metadata and Core Web Vitals held to a budget.
- Documentation sites
- Versioned docs with working code samples, which for a technical product is marketing.
- Analytics and attribution
- Privacy-respecting measurement that answers where the good enquiries came from.
Problems this solves
- Problem
- The marketing site is slow, and that is costing rankings and enquiries.
- Approach
- Rebuild static and server-rendered against a first-load and Core Web Vitals budget enforced in continuous integration.
- Outcome
- The site is fast on a mid-range phone, and stays fast because a regression fails the build.
- Problem
- Every copy change needs an engineer and waits for a release.
- Approach
- Move copy into a typed content model with a clear editing path, so a change is a data edit.
- Outcome
- Marketing ships its own changes, and engineering stops being a bottleneck for wording.
- Problem
- Nobody can say which channel produced the enquiries worth having.
- Approach
- Instrument the funnel end to end with privacy-respecting analytics, and tie enquiry quality back to source.
- Outcome
- Spend follows evidence rather than the last thing someone tried.
How we approach it
Discover
We start from what you want a visitor to do, and from what can be measured without following them around the internet. Most marketing sites are slow because nobody ever set a budget.
Design
Page structure is designed for the queries and the assistants that will quote it as much as for the person reading. Claims are written to be quotable in a single paragraph.
Engineer
Statically rendered, typed, and fast on a phone on a poor connection. Content lives in the repository or in a CMS your team can edit without raising a deploy ticket.
Evaluate & harden
Byte budgets, Core Web Vitals and accessibility gate the build. This site fails its own build the moment the homepage goes over its budget, which is where the habit comes from.
Launch & operate
Analytics that answer a question rather than fill a dashboard, and experiments with a stopping rule agreed in advance. Changes ship without engineering being the bottleneck.
What we build it with
Per-route metadata generated from the content module — a unique title, description and canonical for every page, with nothing to keep in step by hand.
/** Every route earns its own title, description and canonical. */
import type { Metadata } from "next";
export async function generateMetadata(
props: PageProps<"/services/[slug]">,
): Promise<Metadata> {
const { slug } = await props.params;
const service = services.find((entry) => entry.slug === slug);
if (!service) return {};
const url = `${site.url}/services/${service.slug}`;
const { title, description } = service.seo;
return {
title,
description,
alternates: { canonical: url },
openGraph: {
type: "website",
url,
siteName: site.name,
title,
description,
},
};
}Languages
- TypeScript
Frontend & mobile
- Next.js
- React
- Tailwind CSS
Cloud, DevOps & platform
- Vercel
- Cloudflare
- CDN & edge
Questions we get asked
Why hire an engineering firm for a marketing site?
Because for a technical product the site is a demonstration. Performance, accessibility, structured data and a content model your team can actually edit are engineering problems, and they are the ones that separate a site that converts from one that merely exists.
Can our marketing team edit it?
Yes. Content lives in a typed model with validation, so an edit is a data change rather than a code change, and a malformed record fails the build instead of shipping a broken page. If you need a CMS, the same model becomes its schema.
Do you do the writing as well?
We structure it, write the technical content and edit for clarity. For brand and campaign copy we work with your writer or agency — we are engineers who write clearly, not a copywriting shop, and it is better to say so.
How do you measure it without invasive tracking?
Server-side, cookieless analytics wherever it answers the question, with consent handled properly when it does not. You get funnel and source attribution without a page weighed down by third-party scripts you cannot audit.
Tell us what you are trying to ship.
A first call is 30 minutes and costs nothing. Bring the problem rather than a spec — the useful part is usually working out whether this is the right shape of solution at all.
contact@algologix.coWe reply within 24 hours.