Web development pricing in Singapore, without a price list

Offload Foundry does not publish a price list, and this page is not a soft version of one. The reason is that the price follows the scope, and the scope is not knowable before a conversation about what you are actually trying to build.

A published range from an agency that has not seen your requirements is a number chosen to be clicked on. It is either low enough to get the meeting and then revised upwards, or wide enough to be useless — a range spanning an order of magnitude tells you nothing you did not already know. Neither is worth putting on a page that is otherwise trying to be checkable.

What is publishable, and what the rest of this page sets out, is everything about the money that does not depend on your scope: how you get to a fixed number, when each part of it is due, what is billed separately, what happens if the project stops, and what actually moves a quote up or down. Those are the parts most agencies leave vague, and they are the parts you can hold someone to.

The honest cost of that position, stated plainly: if you are comparing three agencies on price alone, this one makes that harder, and a firm publishing a fixed package price is easier to shortlist. That is a real disadvantage and it is the trade for not being quoted a number that was invented before anyone read your requirements.

There are two documents, and the difference between them is worth understanding before you commit to anything, because only one of them costs money.

• The written quote — free, and produced first. It follows a scoping conversation about what you are trying to build, and it sets out what will be built, the milestone schedule with dates, and the fee. It holds for 30 days. You have a number before you have spent anything.
• The detailed specification — the first milestone, and billed. Accepting the quote starts the 10% milestone, which pays for detailed requirements gathering and scoping. That phase produces the specification the rest of the work is built against. It is deliberately the first thing that happens and the smallest thing you pay for.

The practical consequence is that the largest commitment you make on the least information is 10% of a fee you already agreed in writing — and if the detailed scoping changes the picture, that is the point at which it changes, rather than at the end. Changes to scope after that are quoted before they are done, not discovered on the final invoice; the wording is in section 3 of the Terms.

Every engagement is billed against the same four milestones, each invoiced when it is reached and signed off. The percentages never change; the fee they are percentages of is what the quote fixes.

• 10% — on engagement. Payable before detailed requirements gathering and scoping begins.
• 40% — on commencement. Payable before build work begins. This is what reserves your slot in the schedule.
• 30% — at the mid-project milestone. Payable when the milestone named in your proposal is delivered for your review. You are looking at working software, not a status update.
• 20% — on delivery. Payable on final handover, before the work goes live under your control. Intellectual property transfers to you on receipt of this payment.

Invoices are due within 14 days of issue. Third-party costs incurred on your behalf — hosting, domains, paid APIs, licences — are billed at cost and are separate from the fee, so you are never paying a margin on someone else's invoice. Offload Foundry is not GST-registered, so no GST is added to any of it. The full wording is in section 4 of the Terms.

Since the number cannot be published, the next most useful thing is what it responds to. These are the things that change a fee materially, roughly in order of how often they are the deciding factor:

• How much of it is genuinely bespoke. A brochure site with content you supply is not the same project as an application with accounts, permissions and a data model built around how your business works. Most of the cost lives in the second kind, and most of the value does too — but if the first kind is what you need, that is what you should be quoted for.
• Integrations with systems that already exist. Talking to an accounting system, a CRM, a payment provider or an internal database is usually the least visible and most expensive part of a build, because the cost is set by the other system rather than by this one. An integration with a well-documented API is a different size of job from one without.
• Whether the content and design are supplied or produced. Copy, imagery and brand direction take time whoever does them. Supplying them lowers the fee; producing them is real work and is quoted as such.
• How many distinct kinds of user there are. One public visitor is one interface. A visitor, a logged-in customer and an internal admin is three, and the permission rules between them are a fourth thing.
• What happens after launch. A one-off handover and an ongoing retainer are different commercial arrangements, and which one you want changes how the build is scoped — some decisions are cheaper if the same people are still there in a year.
• Urgency, but less than you would expect. Timelines here are usually weeks rather than months because AI is built into the delivery cycle, so a normal deadline is rarely the thing driving the price. A genuinely immovable external date can be, because it removes options.

And the thing that does not move it: search visibility. SEO and AEO ship with every build as standard — server rendering, semantic markup, per-page metadata, canonical tags, an XML sitemap, structured data, crawler rules and an llms.txt. It is not a line item, an upsell or a retainer, because it is close to free at build time and expensive to retrofit. How that works is set out on the bespoke development page, and this site is its own reference implementation — /llms.txt (opens in a new tab) and /robots.txt (opens in a new tab) are the two fastest ways to check whether that claim is true.

Either side can end an engagement in writing at any time, and what happens to the money does not depend on who ended it:

• Milestones already delivered are payable and are not refundable.
• Work in progress on the current milestone is billed for the time actually spent on it, and anything paid beyond that is refunded.
• Milestones not started are not billed, and anything prepaid on them is refunded in full.

Work completed to the point of cancellation is handed over once those amounts are settled. The full wording is in section 5 of the Terms.

The cost that catches people out is not the build, it is the decade afterwards. Two things about it are worth knowing before you compare quotes.

The first is that you are not locked in. All intellectual property in what is built for you transfers to you on final payment; you do not license it back, and handing the repository to another developer is a normal thing to do rather than a breach of something. The one carve-out is the general-purpose components brought to every project, which stay owned here but come with a perpetual, worldwide, royalty-free licence to use inside your product. There is no recurring fee to keep using what you paid for. It is section 6 of the Terms.

The second is the shape of the running cost itself. A server-rendered site on managed hosting has no database on the public internet, no plugin to keep patched and no admin login to be brute-forced — which removes the most common way a small-business site becomes an emergency, and with it the kind of maintenance retainer that exists mainly to prevent one. What remains is hosting and domains, billed at cost, and whatever changes you actually want.

If you do want an ongoing arrangement, there is one standing offer: bring this agency in at the start of a new product rather than after it is built, and the long-term retainer that keeps it running afterwards is discounted. That is a build-with-us-from-the-start offer rather than a general discount on maintaining something someone else built — maintaining a system designed here is genuinely cheaper than inheriting one that was not, and the pricing reflects that. The rate is set out in your proposal alongside the build.

The same section exists on the about page, for the same reason: on a page about money, what is withheld matters as much as what is stated, and you should not have to work out which is which.

• No price list, no range and no starting-from figure. Nothing here is a hint at one either. Ask, and you will get a real number for a real scope.
• No hourly or day rate. Engagements are quoted as a fee against milestones, not as time. Time is billed only in one place — work in progress on a cancelled milestone.
• No package tiers. There is no bronze, silver or gold, and no feature deliberately withheld from a cheaper option.
• No GST. Offload Foundry is not GST-registered. That is a fact about the business rather than a discount, and it is the same fact the Terms and Privacy Policy are written around: this is not a registered legal entity.
• No grant funding. Engagements are not claimable under the pre-approved-vendor schemes, because that listing requires ACRA registration. The position is set out in full on the AI adoption workshops page, including when a listed vendor is the better choice for you.

Describe what you are trying to build and you will get a scoping conversation and a written quote — scope, milestone dates and a fixed fee, valid for 30 days — before you have committed to anything. If the honest answer is that your project does not need a bespoke build, you will get that instead. Start a project or email sales@notify.offloadfoundry.com. A human replies within two business days.