Skip to main content
← Services Index SHEET 02 / 02 · REV 2024
§ 02 / Services Catalog

Website
Design.
Mobile · Content · Care.

Mobile-responsive websites, technical content writing and ongoing maintenance — built by engineers who know what "production" means and what it costs to keep a site alive.

SCOPE

Build · Write · Maintain

Mobile-first · Technical copy · Long-term care

DURATION

2–8 weeks

Build sprint, then optional care contract

DELIVERABLES

6+ artefacts

Site · Content · Care Plan

Discuss Your Web Project Read the Methodology
DESKTOP · 1280px MOBILE · 360px REFLOW W · 1280 RESPONSIVE · LAYOUT SPEC.003 · REV.A

FIG. 03 — Desktop · 3-col grid reflows to Mobile · 1-col

Mobile-First
Designed for 360px first, scaled up
PWA-Ready
Installable web app shell
Zero-Build
Static + CDN · no compile step
WCAG AA
Accessibility targeted by default
§ 01 / Scope of Work

What this engagement covers.

The Website Design engagement covers the build, the words, and the ongoing care. We design mobile-first, write for humans (and search engines), and stay on for as long as you want us to keep the site alive — updates, security patches, content refreshes.

CLIENT
Consultancies · Contractors · OEMs · Service Businesses
STACK
HTML · Tailwind · Alpine.js · Static + CDN
STANDARD
WCAG 2.1 AA · Schema.org · Open Graph · sitemap.xml
OUTPUT
Live Site · Content Bank · Care Plan · Source Files
REPORTING
Uptime · Lighthouse score · Search console (monthly)

Three Build Disciplines

Each discipline produces a real deliverable — the design files, the words, or the care plan.

  • 01 Mobile-Responsive Websites — HTML / Tailwind / Alpine, PWA-ready
  • 02 Technical Content Writing — service pages, FAQs, case studies
  • 03 Support & Maintenance — uptime, patches, content refreshes
  • 04 SEO Foundation — meta, structured data, sitemap, robots
  • 05 Performance Budget — Lighthouse 95+ on mobile and desktop
  • 06 Accessibility (WCAG AA) — keyboard, contrast, screen-reader verified
§ 02 / Methodology

A four-pass build-to-care cycle.

Discovery → wireframe → design → develop → launch → iterate. Analytics-driven improvement.

A site that looks fine in a desktop screenshot but breaks on a phone in a tunnel is broken. We discover, design, write, then stay for the long haul — closing the loop most agencies leave wide open on launch day.

01
PHASE · DISCOVER

Discovery & Information Architecture

Stakeholder interviews, audience model, sitemap, content inventory, and a written brief that fixes scope before any pixels move. We do not start designing a site we cannot describe.

DURATION · 1 WEEK
02
PHASE · DESIGN

Design & Build

Mobile-first layouts in HTML + Tailwind, Alpine.js for any interactive surfaces, static output ready for any shared host. All breakpoints tested on real devices, not just emulators.

DURATION · 2–4 WEEKS
03
PHASE · CONTENT

Content & SEO

Technical copy for service pages, FAQs, case studies. Schema.org structured data, Open Graph cards, sitemap, robots.txt — wired in before launch, not bolted on after.

DURATION · 1–2 WEEKS
04
PHASE · CARE

Launch & Care

Hand-off with a written care plan: hosting, backups, dependency updates, content edit guides, and an optional monthly care contract if you would rather not own the patches yourself.

CADENCE · MONTHLY OR ON-CALL
§ 03 / Deliverables

What you receive on day one.

Every artefact below is produced during the engagement and handed off in editable source format. Content ships as plain Markdown so non-technical owners can edit without breaking the layout.

DOC · SIT · 001

Live Website

Mobile-first responsive site, PWA shell, Lighthouse 95+ on mobile and desktop.

DOC · CNM · 002

Content Bank

Service pages, FAQs and supporting copy in Markdown — editable by anyone with a text editor.

DOC · SEO · 003

SEO Foundation

Meta tags, Schema.org JSON-LD, Open Graph cards, sitemap.xml, robots.txt — wired in, not bolted on.

DOC · SRC · 004

Source Files

Full HTML / CSS / JS source in a Git repo with branch-per-version history you actually own.

DOC · A11 · 005

Accessibility Audit

WCAG 2.1 AA statement, screen-reader pass, keyboard-only nav verified before sign-off.

DOC · CAR · 006

Care Plan

Hosting handoff, backup policy, dependency update schedule, content edit guide.

DOC · PWA · 007

PWA Install Bundle

manifest.json, icons (72–512px), service worker — Android + iOS install ready.

DOC · LIG · 008

Lighthouse Scorecard

Performance, Accessibility, Best Practices, SEO score per page on mobile and desktop.

DOC · OPS · 009

Operations Manual

Plain-English guide to deploy, rollback, edit content and rotate secrets without a developer on call.

§ 04 / Why ConcreteInfo

Sites built for editors, not for the launch vendor.

The hardest part of a website is not the launch — it is the second year, when the original agency is unreachable and you still need new content, a security patch, or a fresh service page. We design for that day before it arrives.

01

Editor-friendly by default

Content ships as plain Markdown. You edit a page by opening a text file — no builder lock-in, no proprietary re-export every time a tool disappears or a vendor stops answering.

02

Written for your audience

Technical copy by engineers who can read a sieve analysis and write about it without marketing fluff. The same content that ranks on Google is the content your prospect will read end-to-end.

03

Care plan is the deliverable

We hand off an Operations Manual and offer a monthly care contract — patches, backups, content edits, dependency updates — so day-365 looks the same as day-1.

§ 05 / Frequently Asked

Pre-engagement questions, answered.

Q.01

What stack do you build on, and who owns the source afterwards?
HTML, Tailwind CSS and Alpine.js — no proprietary builder, no per-page licence. The full source ships in a Git repo under your name on day one. If we vanish, any front-end developer can pick it up next morning.
Q.02

Can my team edit content without breaking the layout?
Content is written as Markdown — a plain text file with simple formatting rules. The Operations Manual shows your team how to add a service, edit a phone number, or attach a PDF without touching layout code.
Q.03

How do you keep the site fast after the first year?
The site ships with a Lighthouse budget so regressions are visible. The optional care contract runs Lighthouse, applies dependency updates, refreshes SSL, and trims content drift — typically a few hours a month, not a full retainer.
Q.04

Can you migrate our existing WordPress site away?
Yes. We extract pages, copy, images and PDFs into static HTML, set up 301 redirects from the old URLs, and stand the new site up before switching DNS. Most WordPress migrations complete in under a week with zero visible downtime.
Q.05

Is the design system documented so we can extend it later?
Every site ships with a one-page design system reference (colors, fonts, spacing, components) plus the source files. New pages and components follow the same rules by default — not because of process, but because we use the same Tailwind tokens everywhere.
§ END OF DOCUMENT · SVC / 03

Have a site that's
drifting without anyone caring for it?

Send us the URL and the rough budget. We respond within 24 hours with what we would actually build, what it would cost, and where the cheap cuts would land you in trouble.

Send a Web Brief Talk on WhatsApp

Phone: +91-9930954848 · Email: services@concreteinfo.in