What the price actually buys.
Four project scopes at published prices, week by week: an entry website at ₱75,000 in two weeks, a 5–8 page business website at ₱120,000 in three to four, a booking and reservation system at ₱280,000 in five to eight, and a custom web application at ₱650,000 in ten to sixteen. Each one says what is included, what is not, and what moves the number. These are illustrative scopes built from our published catalogue — not client projects. The clients are named separately on how we work.
These are scopes, not client stories.
Every figure and duration below is read from the same catalogue that prices /pricing, so the two cannot disagree. The scopes themselves are composites written to explain what a price includes. They describe no client, carry no client outcomes and quote no performance figures — because a number we did not measure is worth less than nothing beside the ones we did.
Entry website
A business with no site, or one that is actively embarrassing, and a first real budget.
Catalogue entry: Ignite — Entry Website
Structure agreed. Four pages, chosen from what you actually sell rather than from a template's menu.
Build from the component library. No custom design — this is the trade that makes the price and the two weeks possible.
Your copy in, images optimised, forms wired to a real inbox, analytics on.
Speed and mobile pass on a mid-range Android, then launch.
- Four pages
- Component-library design
- Contact form to a real inbox
- Analytics
- Mobile and speed pass
- Custom design
- Copywriting (₱55,000 separately)
- Photography
- CMS
- E-commerce
Nothing, by design. It is a fixed price in a fixed two-week slot — if the scope grows, it stops being this product and becomes the one below.
Business website, 5–8 pages
An established business whose site is losing them credibility against competitors.
Catalogue entry: Tailored Website (5–8 pages)
Positioning and structure. What each page has to do, and what happens to the visitor who is not ready to buy.
Custom design on the real content, not on lorem ipsum. Desktop and phone together.
Build, CMS so you can edit without calling anyone, schema and metadata written to fit, analytics.
Speed, accessibility and mobile-data testing, then launch and handover of every account.
- 5–8 pages
- Custom design
- CMS
- SEO foundation and schema
- Analytics
- Accounts transferred to you
- Copywriting
- Photography or video
- Accounts, logins or bookings
- Payments
- Ongoing content
Page count past eight, a language variant, a migration with rankings to protect, or integrations with anything you already run.
Booking & reservation system
A resort, hotel or clinic paying 15–20% to the OTAs for bookings it could take directly.
Catalogue entry: Booking & Reservation System
The availability model. Room or resource types, seasonal rates, the rules that must never double-book. This is the part that decides whether the rest works.
Deposit and cancellation rules as the business actually enforces them, not as a plugin assumes.
Payment capture that reconciles, confirmations, and reminder sequences aimed at no-shows.
Channel sync with the OTAs that already hold inventory, then a live pilot before switching over.
- Availability engine
- Deposits and cancellation rules
- Payments
- Confirmations and reminders
- Channel sync
- Staff view
- The booking-driving website itself
- OTA contract renegotiation
- Front-desk hardware
- Ongoing rate management
Number of properties, an existing property management system with an undocumented API, per-room-type rate rules, and how many OTA channels must stay in sync.
Custom web application
An operation running on spreadsheets and group chats that has outgrown both.
Catalogue entry: Custom Web Application
Discovery. Roles, permissions, and the states a record can be in. Every role added here multiplies what must be designed and tested.
Data model and the integration surface — which existing systems must be read from or written to, and what they actually expose.
Build in working increments. You see a usable slice every two weeks rather than a demo at the end.
Real-data migration, user testing with the people who will live in it, training, and handover of the repository.
- Multi-role and permissions
- Custom data model
- Integrations
- Migration of real data
- Training
- Code and repository yours
- A marketing website
- Mobile apps (₱750,000 separately)
- Ongoing feature work
- Third-party licences
Undocumented systems you must integrate with, roles discovered late, and decision latency — this is priced assuming feedback in about two business days.
A number we did not measure is worth nothing.
Most agency case studies open with a percentage. Very few say what was measured, over what period, against what baseline, or who did the measuring — which is what makes the percentage meaningless even when it is true.
We would rather show you the scope and let you judge whether we understand the problem. When we publish an outcome it will name the client, state the method, and be checkable by asking them.
Until then the honest evidence is the things you can verify right now: published prices, this site’s own measured performance, the sourced market data we publish for anyone to use, and the clients named on how we work.
None of these is your project
They are shapes, not quotes. The Advisor scores the full catalogue against your goal, stage and budget and gives you an itemised figure in about ninety seconds, without an email address.