What a website costs, and what moves the number
Three website packages with published starting prices, because the scope is bounded enough for a floor to mean something. Custom systems carry no starting figure, and the reason is further down this page rather than in a footnote.
Website packages
Starter · Get Online
RM1,200
A business that is just starting, a personal brand, a single service, or a one-off event. You need one place that can be found, that explains what you do, and that people can contact you from — now, not in six months.
Example structure
A single page of roughly five to seven sections: hero, about, services, why you, gallery or portfolio, contact, footer.
Planning
- Agreeing what the site is for
- Identifying who it speaks to
- Section order and content structure
- Where the calls to action sit
Design and build
- Custom interface design from your existing branding
- Responsive on desktop and mobile
- Contact form and a direct WhatsApp link
- Google Maps and social links where needed
SEO and technical basics
- Semantic HTML and a correct heading hierarchy
- Page title, meta description and social share card
- Image alt text, favicon, sitemap and robots
- SSL/HTTPS and basic performance work
2 rounds of revision within the agreed scope30 days of post-launch bug support
Not included by default
- A content management back end
- A blog or articles module
- Google Analytics and Search Console setup
- Additional languages
- Copywriting
- Professional photography and video
- E-commerce and online ordering
- A booking system
- Membership or user login
- A custom back end or dashboard
- Long-term maintenance after launch
Choose this when
- You have no website at all right now
- There is not much content — one page holds it
- You are pushing one service or one event
- You do not need to edit the content yourself yet
- Where most companies should start
Business · Build Trust
RM2,500
A company already trading. Clients look you up before they call, and what they find decides the tone of that call. Services, work and contact each need room instead of sharing one page.
Example structure
Up to five pages — for example home, about, services, work, contact. The actual structure is planned around your business.
Strategy and planning
- Requirement discovery and business goals
- Sitemap and information architecture
- The enquiry path — where people arrive and where they contact you
- A review of peers and reference sites
Design and build
- Custom UI/UX design across up to five page layouts
- A consistent design system — buttons, cards, forms
- Responsive across desktop, tablet and mobile, built from reusable components
- Form validation, a custom 404, and a CMS or blog where it earns its place
SEO and discoverability
- A unique title and meta description per page
- Canonical URLs, sitemap, robots and social share cards
- Structured data where it genuinely applies
- Google Analytics 4 and Search Console connected
Performance and delivery
- Image optimisation and lazy loading
- Core Web Vitals and a mobile performance check
- Cross-device testing and production deployment
- Verification that analytics and SEO setup actually work after launch
3 rounds of revision within the agreed scope30 days of post-launch bug support
Not included by default
- Additional languages
- Copywriting
- Professional photography and video
- E-commerce and online ordering
- Payment gateway integration
- A booking system
- Membership or user login
- A custom back end or dashboard
- Complex database development
- Advanced API integration
- Advanced animation and 3D
- An ongoing SEO, GEO or content campaign
- Long-term maintenance after launch
Choose this when
- You need a proper company website
- Three to five pages covers it
- Credibility is the main objective
- You want to update some content yourself
Growth · Grow Online
RM3,500
A company with more services and more to say. The site has to start producing enquiries rather than merely existing — services need pages of their own, the blog has to keep growing, and the structure has to hold pages added for years.
Example structure
Up to ten pages — for example home, about, a services index, three service detail pages, work, blog, FAQ and contact. The actual structure is planned per project.
Strategy and planning
- Deeper requirement discovery and goal analysis
- Customer journey and conversion path planning
- A sitemap of up to ten pages, with a content hierarchy
- Service-page strategy — which services deserve a page of their own
Design and build
- A full custom UI/UX system across up to ten pages
- Reusable component architecture and content structures
- CMS, blog and categories
- Standard third-party integrations and scroll motion
SEO, AEO and GEO technical foundation
- Page-level metadata, canonical URLs, sitemap and robots
- Organization, FAQ and other structured data where it applies
- An internal linking structure and a searchable service-page structure
- Content structured so AI search engines can read it
Performance and delivery
- A performance pass over images, fonts, bundles and lazy loading
- Core Web Vitals and mobile performance QA
- Technical SEO QA and Search Console verification
- Cross-device QA and production deployment
3 rounds of revision within the agreed scope30 days of post-launch bug support
Not included by default
- Additional languages
- Copywriting
- Professional photography and video
- E-commerce and online ordering
- Payment gateway integration
- A booking system
- Membership or user login
- A custom back end or dashboard
- Complex database development
- Advanced API integration
- Advanced animation and 3D
- An ongoing SEO, GEO or content campaign
- Long-term maintenance after launch
Choose this when
- You have several services, each needing to be explained properly
- Roughly six to ten pages
- The blog and content will be an ongoing effort
- You want the site to actually produce enquiries
Growth includes the technical foundation for SEO, AEO and GEO — structure, metadata, structured data, internal links. It is not an ongoing SEO campaign, not keyword optimisation, not link building, and it promises no ranking. The foundation decides whether you can be found; ranking comes from content and time after that.
When a package is the wrong shape
All three packages above solve the same kind of problem: be found, be understood, be contacted. If what you actually need is for part of the business to run online — taking orders, handling bookings, tracking stock, letting customers log in and check things themselves — that is not a website's scope, it is a system. Forcing it into a package ends either in something that does not work or in a price nobody can hold.
Any of these, and it should be scoped as a system
- Customers need to order or pay online
- There are bookings, schedules or limited slots to manage
- People log in, and different people see different things
- Stock, orders or member records have to be stored and looked up
- It has to connect to accounting software, WhatsApp or a supplier's system
- You and your team need an admin screen to run all of it
These start with a free diagnostic that settles the scope before any quotation — so you never receive a figure for something neither side has defined yet.
What moves the figure
How the final figure is reached
Base package + scope adjustment + add-ons + additional complexity = final quotation
Scope
Whether we are solving one step or an entire process. Automating order entry and building a system that spans orders, inventory and accounts are not the same order of investment.
Process complexity
Whether your processes are already standardised. If the same task is handled differently by different people, the first job is to settle the process — that is real work, and skipping it costs more later.
Integration
Which existing systems have to connect: accounting software, payments, WhatsApp, marketplaces, supplier systems. The difficulty is rarely the count — it is how open each one is.
Long-term support
How deep the relationship needs to be after delivery: keeping it running, or evolving it as the business changes. This determines total cost of ownership, which is usually worth more attention than the initial figure.
How a quotation is produced
Free diagnostic
An unpressured conversation about the business and how it currently runs. No quotation at this stage. You leave with a read on where things stand, even if we never work together.
Scope definition
We write down what is in and, just as importantly, what is deliberately out. Excluding things explicitly is what makes a quotation hold up and keeps the project free of later disputes.
Formal quotation
A proposal setting out scope, deliverables, timeline and who is accountable for what. The figure is calculated, and we explain how it was reached.
Where the boundaries are
- Diagnosis before quotation
- We do not put a figure on work we have not understood. A quotation produced from a feature list is usually discovered to be wrong halfway through the build.
- Feature count ≠ complexity
- A feature involving booking, calculation, authentication, permissions or a third-party API is not the same work as a content page. Scope is assessed by complexity, not by count.
- Revision ≠ new requirement
- Adjustments within the agreed scope are revisions. New functionality is a scope change and is re-scoped and quoted. This protects both sides.
- Support ≠ unlimited changes
- Post-launch support covers bugs and technical issues within the agreed scope. New pages, content changes, new features and redesigns are additional work, and are identified as such.
- Content is client-provided by default
- Unless arranged otherwise, company information, product descriptions, images, logo and legal content are provided by the client. Copywriting, photography and video are separate services.
- Additional languages are separate scope
- A second language is not a second copy of the text. Pages, metadata, SEO structure, QA and every future content update multiply with it. This site is trilingual, so that is experience rather than a disclaimer.
- We do not compete on price
- If the lowest quotation is the deciding factor, we are probably not the right fit — and we will say so directly rather than take the work and manage it later.
Questions people actually ask
- Is RM1,200 the final price?
- It is a floor, not a fixed price. A single-page site with a clear scope and content ready can land close to it. If a page needs a calculator, filtering, or a connection to another system, that is different work and is quoted separately. A figure always follows seeing what you actually need.
- Why is there no starting price for custom systems?
- Because the range is too wide to mean anything. A form that files bookings into an admin screen and an operations system spanning orders, inventory and accounts are an order of magnitude apart. A rough figure would either scare off the small project or be one we could not honour. These start with a free diagnostic that settles the scope.
- Will the price keep going up mid-project?
- Changes inside the agreed scope do not cost more; new requirements do. The line is written on this page under “Where the boundaries are”: adjusting a section's layout is a revision, adding a membership system is a new requirement. The scope is written down before the quotation, so both sides are reading the same document.
- Someone quoted me less. How do I compare?
- Compare the same scope. Most of the difference sits in scope and in who is responsible afterwards, not in a unit price: who writes the content, how many revisions, how long someone answers after launch, how deep the SEO structure goes, what it costs to add pages later. If the scope really is identical and we are still more expensive, we may not be the right choice — and we would rather say so than take the job and work it out later.
Not sure which one fits?
That is the normal starting position, and it is what the diagnostic is for. Six questions, about three minutes, and you see where you are before anyone quotes anything.
Take the free diagnostic→