Skip to content

Web development · revamps Studio

Web development that turns traffic into enquiries.

revamps plans, builds and instruments marketing websites and web platforms: pages structured around one action, a CMS your team edits without a ticket, tracking verified before launch, and every enquiry routed to a named person.

STUDIO / WEB DEVELOPMENT
  • Tracking verified before launch
  • Core Web Vitals tested at handover
  • Your team edits in the CMS
  • Colombo team · Sri Lanka and international

The problem

It looks like a website. It works like a brochure.

Visitors arrive from ads, search and referrals, read a page and leave. Enquiries land in an inbox nobody owns, and nobody can say which channel produced the last one, so every redesign is a guess. We rebuild structure, editing, tracking and routing together. Now the site reports what it earns.

  1. 01

    Traffic without action

    Visitors cannot tell what you do, who it is for or what to do next from the first screen, so they leave without acting.

  2. 02

    Every edit needs a developer

    A price change or a new landing page becomes a ticket. Campaigns launch late or point at the wrong page.

  3. 03

    Enquiries that leak

    Forms email a shared inbox, WhatsApp messages wait, and nobody owns the reply time.

  4. 04

    No idea what works

    Without event tracking, ads, SEO and referrals look the same. Budget follows opinion instead of evidence.

  • EXAMPLE — HOW IT WORKS
  • TRACKING / VERIFIED BEFORE LAUNCH
  • ORANGE HIGHLIGHTS THE ACTIVE PATH OR RESULT

How a revamps website works

Page. Action. Signal. Follow-up. One system.

Every build follows the same path. A visitor arrives, the page makes one next step obvious, the action fires a tracked event with its source attached, and the enquiry reaches a named person while it is still warm. The design sits on top. This is what it is for.

Hover or tap a node

Illustrative system map, not client data. The CMS sits under nodes 02 and 03: your team edits pages and forms without a developer.

The process

From first call to a site you can measure.

Five steps, each closed by a sign-off, so scope is settled before development starts and the design is not reopened in week six.

  1. 01

    Enquiry and reply

    You tell us what the site has to do. We reply with the questions that matter, not a template proposal.

    Within 2 business days

  2. 02

    Audit and scope

    We review the current site, analytics access and conversion path, then send a written scope: pages, integrations, timeline.

  3. 03

    Structure and direction

    Sitemap, page wireframes, messaging order and the component model, signed off before development begins.

  4. 04

    Build and QA

    Components, CMS, integrations and tracking, tested on real phones, against Core Web Vitals targets, with every form submitted end to end.

  5. 05

    Launch and first 30 days

    Go live with tracking verified and your team trained on the CMS, then fix what real usage shows first.

What's included

Design is the part you see. The system is the part that pays.

Six workstreams in every build. Depth changes by tier: page count, integrations and how far the tracking reaches.

  • Information architecture

    What each page must say, which action it drives and how content is grouped. Agreed before design starts.

  • Conversion structure

    Messaging order, proof placement and one primary action per page. Copywriting is scoped separately when needed.

  • Components and CMS

    Reusable sections your team assembles into new pages, so a campaign launches without a rebuild.

  • Speed and technical SEO

    Metadata, structured data, crawlability and Core Web Vitals, checked before handover.

  • Tracking and lead routing

    Tag Manager, GA4 events and form routing to the inbox, chat or CRM your team uses, tested end to end.

  • Launch and handover

    CMS training, access to every account and a written list of what to improve next.

Acceptance targets

Know the targets before the build. Check them at handover.

  • ≤ 2.5 s

    Largest Contentful Paint

    Mobile load target at the 75th percentile, tested at handover

  • ≤ 200 ms

    Interaction to Next Paint

    How quickly the page responds to a tap

  • ≤ 0.1

    Cumulative Layout Shift

    Nothing jumps while the page loads

Targets: Google Core Web Vitals 'good' thresholds (web.dev/articles/vitals).

View the case study

Work

Judge the work, not the pitch.

Fit

You don't need the cheapest quote. You need the right fit.

We do our best work with teams who can name the action the site should drive. A short scoping call tells us both quickly.

  • A good fit if

    You can name the action the site must drive. You want tracking and will read it. One decision-maker can review work weekly.

  • Not a fit if

    You are choosing on the lowest quote. You want unlimited revisions instead of decisions. You would rather not see the numbers after launch.

Questions

Ask before you commit. Get it in writing.

Can our team update the website without a developer?

Yes. Sites are built from reusable sections in a CMS, so your team edits text, images and new pages without a ticket. Handover includes a training session and written notes.

Do you set up tracking and analytics?

Yes, on every production launch. We configure Google Tag Manager and GA4 events for the actions that matter, attach the traffic source to each enquiry, and submit every form end to end before go-live.

Do you work with clients outside Sri Lanka?

Yes. revamps is based in Colombo (UTC+5:30) and works in English. Scope, sign-offs and progress are written down, so time zones change when we talk, not what gets delivered.

Can revamps work inside an existing design direction?

Yes. revamps can extend an existing brand and UI language while tightening hierarchy, conversion flow and component reuse.

Can you rebuild only part of a website first?

Yes. A phased rollout can focus on the highest-leverage pages first, then expand into the rest of the site once the core system is in place.

Enquire

Tell us the goal. We'll come back with the scope.

Four short fields, about a minute. We reply within 2 business days with the questions that set the scope and a time for a short call. No automated sales sequence.

Prefer email? [email protected]

Fields marked * are required.

Who it is for, what visitors should do, and your current URL if there is one.

After launch

After launch: keep it fast, secure and found.

A website is not finished at launch. Hosting keeps it fast, maintenance keeps it secure and current, SEO keeps it found. Each has its own page.

  • Illustration of a dark infrastructure dashboard with a latency line chart, a world map of server locations, a server tree and a rack unit.

    Hosting

    Managed hosting for websites and web apps, run as one measured layer of the system: uptime, server response and errors checked all month, backups restored to prove they work, and a named person who responds when something breaks and writes down why.

  • Illustration of a dark site-health dashboard with a check-marked status ring, a calendar, security, bug and backup status tiles, and a task list.

    Maintenance

    Maintenance for the site you already have: updates tested before they go live, security patches, the changes your team can't make, every form and link checked monthly and a written report, with set hours and a reply time on every plan.

  • Illustration of a dark search analytics dashboard with a rising red line chart, donut charts, a site-structure tree and a keyword node map.

    SEO

    Search work run as part of the measured system: a site Google can crawl, read and trust, pages planned around what buyers actually type, and a monthly report on the organic enquiries it produces, not rankings alone.