SEMESTA AGROWeb · B2B
Company website for a palm oil IT-Consultant Company
Rebuilt the website of PT Semesta Agri Solusi from a single logo page into a full product site for Green Harvest Plantation, an ERP for palm oil estates, mills and head offices.
- Role
- Initiated and built it: information architecture, UI design, front end and SEO
- Period
- January 2026
- Team
- In-house initiative at PT Semesta Agri Solusi
- Status
- Live
- 10sections telling one story, from hero to offices
- 8ERP modules in the interactive explorer
- 2offices with maps and click-to-call
A logo-only page became a product website the sales team can share in every conversation, and it now brings in requests for demos and presentations.
Context
The problem
The website showed the company logo and nothing else, so it worked against the sales team. The product is a niche ERP covering estates, mills, bulking and head office, which is hard to explain quickly. The audience (plantation owners, finance directors, operations managers) expects industry terms like FFB, CPO and BKM, not generic software language. And the site didn't show up for any relevant search.
Solution
What we built
A multi-page site that tells the story in order: what the product is, why it can be trusted, and how to get a demo. Modules are organised around the client's real structure, explained with an interactive explorer and mockups, backed by client logos, field photos and a demo video, with clear calls to action and full SEO metadata.
- Next.js
- React
- Tailwind CSS
- Motion
- Plesk
Workflow
Approach
- StructureHero, client logos, scope, modules, coverage, advantages, gallery, demo CTA, video, about and offices.
- SimplifyModules grouped as Estate, Mill, Bulking and Head Office, with a tabbed explorer and an auto-scrolling catalogue.
- TrustClient logos, industry-specific advantages, real field photos and a walkthrough of the BKM mobile app.
- ConvertRepeated “Contact for Demo” and “Free Consulting” CTAs, and both offices with maps and click-to-call.
- Be foundIndustry keywords, canonical URL, robots, Open Graph and Twitter cards.
Decisions
Decisions and trade-offs
Organise by the client's business, not by feature
Visitors see Estate, Mill, Bulking and Head Office first, so they find where the system fits their own operation before reading about modules.
Speak the industry's language
FFB, CPO, kernel extraction rate and BKM instead of generic software terms. The audience trusts vendors who already know their work.
Show proof instead of adjectives
Client logos, photos from real estates and mills, and a video of the mobile app do more than any tagline.
My role
What I owned
- Proposed the rebuild myself, as an initiative inside the company.
- Planned the information architecture and page structure.
- Designed the UI and built the front end.
- Built the interactive module explorer, catalogue, logo marquee and filterable gallery.
- Set up SEO and social sharing metadata.
Artefacts
Have a process that should be a system?
I'm not looking for a new role, but I'm always up for a conversation about a system, a process or a collaboration.