RASA × VibeCodersPH · Concept Review
6 directions · 08 Aug 2026
Website revamp · Design direction

Six directions. One decision.

These are not six versions of the same website. Each one is a different bet about what the site is for — who it serves, and which part of the business it grows. Pick the bet first; the styling follows.

ClientRASA Group · est. 1994
ScopeOne site · four companies
CompaniesRealty · Instruments · Drone Vision Pro · QuantumLab
StatusConcept prototypes — not live
The finding that shaped all five

The Projects page has no projects on it.

rasasurvey.com lists ten project categories — airport and port, hydropower, pipeline, transmission line, mining, parcellary — and not a single project inside them. No client names, no dates, no scope, no numbers. The Technology page carries one instrument.

Thirty years of surveying the country's expressways, bridges, dams and grid corridors, and almost none of it is on the web. That is not a design problem. It is the most valuable unbuilt asset in the business, and it is why a procurement officer comparing three firms cannot currently choose RASA on evidence.

How to read these

Two decisions, not one.

Most website reviews collapse into taste. This one shouldn't. There are two separate questions and they have different right answers.

Decision A · Strategy

What is the site for?

Winning tenders? Selling equipment? Proving national coverage? Fixing the content bottleneck? This is a business decision, and it belongs to RASA. The five concepts each answer it differently.

Decision B · Style

What should it look like?

Colour, type, imagery, motion. Easy to change later and cheap to iterate. Do not let this drive Decision A — a direction that looks good but serves the wrong audience is the expensive mistake.

Practical note: it is completely legitimate to say "the strategy of 04, the look of 02." That is a useful answer. What is not useful is "the header of 02 with the colours of 04 and the layout of 01" — that produces a website nobody designed.

The thing worth understanding before you choose

"Generic" is a content problem, not a layout problem.

Look at any well-made contractor or engineering website and you will find the same skeleton: photo hero with two buttons, icon trust strip, sectors, services grid, featured projects, numbered process, testimonials, FAQ, fat footer. It repeats because it works — it is the path a B2B buyer expects to walk, and deviating from it costs trust rather than earning attention.

What makes those sites feel interchangeable is not the skeleton. It is that the contents of the slots are fungible — "450+ projects", "98% satisfaction", "Quality Craftsmanship" could belong to any company in any country.

Put CLLEX, the Bataan–Cavite Interlink Bridge, the RIEGL miniVUX-1UAV, PRS92 and ±7 cm into those same slots and the identical layout stops being generic. Conventional structure, specific substance. That is what Concept 06 is, and it is why it is the recommendation.

The six

Each one fixes a different problem.

06 is the recommendation. The other five exist so the choice is informed — and so their best sections can be borrowed into whichever one wins.

06

The Standard RECOMMENDED

The proven B2B infrastructure pattern, done properly: photo hero with two CTAs, trust strip, sectors, services grid, featured projects, process steps, reviews, FAQ, fat footer. Nothing here is invented — this layout is conventional because it converts, and conservative buyers read convention as competence.
Signature — the whole industry-standard skeleton, filled with RASA's actual specifics
ForEveryone. It offends nobody and converts.
BrandsUtility-bar switcher + Group section
RiskLowest risk on the page
Palette
FixesEverything adequately, nothing brilliantly. The safe, correct, sellable answer — and the one most likely to be approved on Friday.
01

Instrument Grade

The technology leader. Dark, precise, spec-dense — the site reads like a well-calibrated device. This is the direction closest to the CHCNAV reference RASA supplied, and it builds on the design system already produced.
Signature — live point cloud, published sensor tolerances
ForEngineers who compare specs
BrandsTab switcher in the utility bar
RiskSafest — also the least differentiated
Palette
FixesCredibility against international competitors. Baseline, client-endorsed.
02

The National Record

The map is the interface. Thirty years of projects plotted across Luzon, Visayas and Mindanao, filterable by sector. Cartographic, paper-toned, calm. No competitor in the Philippines can copy this — they don't have the thirty years.
Signature — interactive project map of the whole country
ForAnyone asking "have you done this before?"
BrandsFour toggleable map layers
RiskNeeds project data to be real
Palette
FixesThe empty Projects page — turns the biggest liability into the biggest asset.
03

The Bid Book

Institutional authority. Serif, paper, gold rules, a formal Register of Works and an Instrument Register you can hand to a prequalification committee. Built for one reader: the person deciding your shortlist.
Signature — downloadable capability statement
ForGovernment procurement, prime contractors
BrandsFormal group masthead, four divisions
RiskReads conservative — deliberately
Palette
FixesPublic bidding. DPWH-style shortlisting where evidence beats aesthetics.
04

The Exchange

Commerce-led. The instruments and drone arms come to the front with a real catalogue, specs, stock and a quote list — and a 60-second qualifier that scores and routes every enquiry before anyone spends time on it.
Signature — the lead qualifier. Try it in the hero.
ForEquipment buyers, and everyone stuck in Messenger
BrandsFull switcher, commerce is the default
RiskLargest build — needs product data
Palette
FixesThe stated #1 problem — poor lead qualification and cold follow-up. Also monetises the arms currently living on Facebook.
05

The Field Dispatch

The website as a publishing system. Editorial, photography-led, built so one field day produces nine assets — a project record, a long read, LinkedIn posts, a short video, a newsletter item, a capability slide.
Signature — the content engine diagram
ForThe multimedia team, LinkedIn, recruitment
BrandsFour editorial desks under one masthead
RiskHungriest for photography — none exists yet
Palette
FixesRon and Jimbo's bottleneck — repetitive posts, long video edits, falling engagement.

These are not mutually exclusive. If 06 wins — and it probably should — the strongest sections of the others drop straight into it as modules, without changing the skeleton: 02's project map becomes a section above Featured Projects. 04's qualifier replaces the "Get a Quote" form. 03's Register of Works becomes the Projects page behind "View All". 05's field reports become the News section. That is the real outcome of building six — not one winner and five wasted, but a conventional frame with four unusually good parts bolted in.

The decision instrument

Don't ask them which one they like.

"Which do you prefer?" produces taste, hedging, and a Frankenstein brief. Ask these four instead — they produce a decision.

Question 01

Where does next year's revenue actually come from — services, or equipment?

If services and public bidding, the answer is 02 or 03. If equipment sales, it's 04. This single question eliminates three of the five.

Question 02

Picture the person you most want on this site. Who are they?

A DPWH shortlisting officer, a private consultant's project engineer, a buyer comparing GNSS receivers, or a graduate geodetic engineer looking for a job. Each points somewhere different.

Question 03

Can you supply the project records — client, year, scope, instrument?

02 and 03 are the strongest concepts, and both are worthless without this data. If it can't be assembled, say so now and the choice narrows honestly.

Question 04

Is the content bottleneck a website problem or a staffing problem?

If the team will keep producing weekly regardless, 05 multiplies their output. If nobody will feed it, 05 becomes an empty magazine — the worst outcome on this page.

What we need from RASA

Every highlighted block is something only you can supply.

Open any concept and press Highlight placeholders in the bottom bar. Everything that lights up is invented content standing in for something real. This is the content request, made visible.

Blocking

Project records

  • 10–15 flagship projects: client, year, location, scope
  • Instrument used and delivered accuracy per project
  • Permission to name clients publicly
  • CLLEX and BCIB details — already public, already strong
High

Photography & video

  • Crews in the field, instruments in use
  • Drone operations and the aircraft themselves
  • Principal and team portraits
  • Any existing raw footage — even phone clips
  • Point cloud or ortho exports we can render
Standard

Company & product

  • Logo files for all four companies (SVG preferred)
  • Brand colours, if any are documented
  • Equipment specs — 1 or 2 samples to start
  • Accreditations, PCAB, ISO, licences
  • Real figures for the statistics strip

On the numbers: every statistic in these prototypes — 1,240 projects, 86k hectares, 17 regions — is invented to show the layout. None of it goes live unverified. That is exactly what the highlight toggle is for.

Architecture

One site, four companies — solved five ways.

RASA owns all four and wants one site to maintain. That is the right call, and it is a design problem worth deciding deliberately rather than defaulting to tabs.

The options on the table

01 — Persistent tab switcher. Four tabs in the utility bar, always visible. Familiar, cheap, slightly bureaucratic.
02 — Map layers. Each company is a layer you toggle. Elegant, and it makes the group feel like one system rather than four brochures.
03 — Formal divisions. A group masthead with four numbered divisions. Reads as a serious holding company.
04 — Audience-first. The visitor picks what they need; the site routes to the right company invisibly. Best for conversion, hardest to build.
05 — Editorial desks. Four desks under one masthead. Strong if the site publishes; meaningless if it doesn't.