The Problem
Saiko Prime Holdings is a family-led holding company in Pampanga with four businesses under it: construction, building materials, digital solutions for construction, and an in-house media arm. When I started, the first thing I tried to pin down was who actually needs to find this company online. The answer was two very different groups.
- want to know who the company is, what it owns, and how to start a conversation. If their inquiry sits unanswered for a week, they move on.
- are vetting a contractor before trusting them with a lot of money. They want proof: real projects, real specs, and a company that looks like it will still be there when the house is finished.
A single site trying to serve both would end up serving neither well. And an inquiry form that drops messages into a shared inbox is how leads quietly slip through the cracks. So the work had two parts: the right sites for each audience, and a system that makes sure no inquiry is forgotten.
The Fix
A Parent Site With Two Jobs
I gave the Holdings site at saikoph.com two jobs, and put them in order so every decision had a tiebreaker:
- When two design choices pulled in different directions, the one that served investors won. The homepage leads with who the company is, then the four businesses, then news, then the inquiry form.
- Each business gets a card that links out to its own site once that site exists, and says “Website coming soon” until then. An empty card that admits it is coming reads better than a link to a half-built page.
The look follows the company’s brand: metallic gold on near-black, Cormorant Garamond headings, Inter for everything else. I apply the gold as a gradient rather than a flat colour, because flat gold on a screen tends to read as mustard instead of metal.
A Separate Site for Each Business
The bigger decision was how to build the subsidiary sites. One WordPress multisite would have been tidy on paper. I went the other way: each business gets its own WordPress install on its own subdomain (builders.saikoph.com and so on), with its own custom theme. They share no parent theme and no plugin. When a pattern works on one site, I copy it to the next on purpose.
My reasoning: each business sells to different people, launches on its own schedule and changes for its own reasons. I wanted a fix to the construction site’s gallery to be physically unable to break the investor funnel. Separate installs keep every change small and every risk contained. The cost is some copying by hand, and I think that is a fair trade for a client whose investor site has to stay up.
An Investor Pipeline That Follows Up on Its Own
A good-looking site doesn’t help if an inquiry gets lost afterwards. So behind the inquiry form I built a GoHighLevel pipeline with six stages: New Inquiry, Qualified, In Conversation, Follow-up Later, Committed and Declined.
The question I kept asking was: what happens to this person if everyone on the team is busy this week?
- becomes an opportunity at New Inquiry, gets tagged, sends the team a notification with everything the investor wrote, and sends the investor an acknowledgement from the company’s own sending domain. They know straight away that someone received it.
- for three days while it is still at New Inquiry or Qualified, a short check-in goes out. Five days later, if nothing has moved, a second and last note goes out, and a follow-up task is created for a person to pick up. The sequence stops the moment the investor replies or the inquiry moves to a later stage, so nobody gets chased after they have already answered.
- (Follow-up Later or Declined) get at most one update per quarter, and only if they ticked the marketing consent box. If they untick it, they drop off the list.
I designed the form with the rules in mind from the start. The consent checkbox is required under the Data Privacy Act (RA 10173). Questions that could read as soliciting investment stay off the public form entirely; those conversations belong with a person, not a web form.
Privacy Built In From the Start
A Philippine company collecting investor details carries real obligations, so I treated privacy as part of the build rather than something to patch later.
- The company’s attorney revised the privacy policy before the form went public.
- Every theme I build ships with hardening on day one: author archives return 404, the public users endpoint is closed, the users sitemap is off, and link previews carry no author details. These are the quiet places WordPress leaks account names, and they are easy to miss because nothing looks broken.
- Every photo goes through a pipeline that strips metadata, including GPS. Some phone camera apps print the street address and coordinates straight into the image, so I crop those strips off rather than blur them; a blur can still leave enough to read.
- Where a client is under NDA, their name never appears anywhere on the site: not in titles, file names, alt text or image captions.
The Project Page: Melendres-Enriquez Residence
Before designing the Saiko Builders site, I wrote down its three jobs: turn visitors into booked site visits, prove the work with a real project portfolio, and be a credible place to land for people coming from Facebook, the main lead channel in this market.
The project page is where the proving happens. The Melendres-Enriquez Residence is a good example: a three-storey, 443 sqm home in Kawit, Cavite, with a construction period of 2025 to 2026 and Saiko Builders as general contractor from ground-up to completion. It is under construction now, in its architectural and MEPF phase.
I put myself in the shoes of someone deciding whether to trust this contractor with their house. Their first questions are simple: what kind of building, where, when, what role the contractor plays, and what stage it is at. So the top of the page answers exactly those, before anything else. Below that sit the scope of work, the gallery and the construction progress record.
The gallery shows the designer’s renderings: what the house will look like. The first set I received came out of a design proposal PDF that had shrunk every image to 800px, too small for a hero image. I asked for the designer’s full-size originals, and once they arrived I re-processed every image from them. Along the way I left out the frames that should not be published: floor plans of a private home, a streaming logo on a TV screen and branded wall art. One image had a business name reflected in the stair glass, so I blurred it.
Below the renderings sits what the house looks like right now. A construction progress section, “Month by month on site.”, holds real site photos with one tab per month: February, May, July and October 2026 so far. A client can tap back through the months and watch the house go up. Renderings never go in this record. It stays site photography only, so nobody mistakes the plan for the progress.
One lesson from this site now shapes every build I do: The client’s mockup had sections that needed in-progress photos of its completed projects. Those photos don’t exist, and an empty section looks worse than no section. So I cut them.
Galleries also have to handle whatever number of images the client sends, and odd counts used to leave a gap at the end of the grid. I changed the layout so that on phones an odd-count gallery leads with one full-width image, and on a computer the first one to three images take the leftover cells. No row ends on an empty space, whatever the count.
How Updates Ship: Rounds, With a Report
The CEO reviews the live site on her phone and sends her changes. Rather than pushing each change the moment it arrives, we work in : I gather a batch, ship it in one go and report back. It keeps the site stable and gives her one clear update instead of a trickle.
Here is the process I follow for every round, and why each step is there:
- Every photo in the round goes into a plan first: which project, which slot (hero, card, gallery), what order and what alt text. If it isn’t written down, it can’t be checked.
- The importer reads the plan and reports what it would do, without touching the site. This is where mistakes get caught cheaply.
- The same plan runs for real.
- Theme releases go through a deploy tool that backs up the live theme, installs the new one and checks every file against the release. On the latest Builders release that was all 46 files.
- Before anything changes, I screenshot the pages that will change. Afterwards, I screenshot them again. The CEO gets a short PDF listing every change, with a link to each page and a before and after picture, plus a plain message saying what went live.
One round put live in a single pass, from six import plans, with the report sent the same day.
Of all the steps, the report is the one I would recommend to anyone who builds for clients. The client doesn’t have to log in to WordPress or take my word for it. They open the PDF, see exactly what changed, and tap through to the live page.
The Result
- land on a site that looks like the company they are backing, and every inquiry is acknowledged, followed up and handed to a person when it needs one.
- can open a project like the Melendres-Enriquez Residence and see the facts, the scope, the design and the build month by month, in one place.
- sees every change before and after, without logging in, and sends the next round when she is ready.
WordPress with custom themes (no page builder), Secure Custom Fields, GoHighLevel, Cloudflare in front of LiteSpeed.
Got a Problem Like This?
If your business has outgrown its website, or inquiries are slipping through the cracks, I’d be glad to talk it through with you. Tell me the problem, and we’ll work out the fix together.