# Offload Foundry > Offload Foundry is a Singapore-based bespoke web and AI development agency. It builds custom web applications and micro-SaaS products for solopreneurs, founders and enterprises, and helps businesses adopt AI through workshops, staff training and supporting infrastructure. Every build ships with SEO and AEO as standard. ## Key facts - Location: Singapore. Serves clients in Singapore. Not GST-registered. - Offload Foundry was previously known as Web Dev Solutions (webdevsolutions.io). Same founder, same agency, renamed in 2026. - Founder and sole point of contact: Chun Mun Loh, Founding Engineer. - Engagement model: written quote after scoping, valid 30 days; billed across four milestones at 10% / 40% / 30% / 20%; invoices due within 14 days. No price list is published — the price follows the scope. - Intellectual property: everything created for a client transfers to that client on final payment, excluding the agency's own general-purpose reusable components, which are licensed to the client perpetually for use inside their own product. - Response time: within two business days. - Contact: sales@notify.offloadfoundry.com, or the form at https://offloadfoundry.com/#contact ## Services ### Bespoke web applications Custom-built websites and web applications for solopreneurs, founders and enterprises — designed and built for the way your business actually works, rather than fitted to a template. SEO and AEO ship with every build as standard, not as a paid add-on. ### Micro SaaS and products Product work, from an idea to something people can pay for: we design, build, operate and pay for our own products the same way, which is why Offload Foundry publishes four of its own products (OYLIW, Creator Offload, ibuytoto and Tricxter) and is not a portfolio of client logos. ### AI-driven delivery AI is built into how we work, not bolted on as a gimmick — it runs across the whole delivery cycle, from requirements and architecture to implementation, testing and documentation. A small senior team moves at the pace of a much larger one, so working software often arrives in weeks rather than months. ### Quality that keeps up with the pace Speed never comes at the cost of quality. Every line of code is reviewed by a human engineer, and AI works for us on the quality side too — generating test coverage, catching regressions, flagging security and accessibility issues, and enforcing consistent standards on every change. ## Client work - Lansys Pte Ltd (https://lansys.com.sg), 2024 — Designed, wrote and migrated the corporate site for a Singapore network-cabling and IT-infrastructure firm. Scope: Design, Build, Migration, Content. Stack: Next.js, React, Vercel. Full case study: https://offloadfoundry.com/work/lansys ## Products built and operated by Offload Foundry - OYLIW — Offload Your Life In Weeks (https://www.oyliw.com) — A life calendar: it draws a long life as a grid of about 4,680 weeks — one box a week, one row a year — and fills in the ones already lived. The maths and the drawing both happen in your browser. Audience: Anyone who wants to see their own time all at once. Status: live. Stack: Next.js, React, Postgres, Vercel, Cloudflare. - Creator Offload (https://www.creatoroffload.com) — UGC creator management for agencies. Briefs, creator submissions, rights clearance and review run as one pipeline, behind a public REST API and signed webhooks. Audience: Influencer-marketing and UGC agencies running creators across client workspaces. Status: beta. Stack: React, Vite, NestJS, Postgres, Vercel, Private VPS, Cloudflare. - ibuytoto (https://www.ibuytoto.com) — CPF-aware FIRE calculators for Singapore professionals: what freedom actually costs, what a disciplined plan gets you, and how that compares with hoping for a jackpot. Not a lottery site. Audience: Singapore professionals working out when they can afford to stop. Status: live. Stack: Next.js, React, Postgres, Vercel, Cloudflare. - Tricxter (https://www.tricxter.com) — Generates realistic-looking but completely invalid Steam, Apple, Google Play and Amazon gift-card codes, so someone being scammed can waste the scammer’s time instead of their money. Audience: Anyone being pressured into paying a scammer in gift cards. Status: live. Stack: React, Vite, Vercel, Cloudflare. ## How we work ### 1. We scope it together We start with a conversation about what you are actually trying to build, and follow it with a written quote setting out the scope, the milestones and the fee — which holds for 30 days. ### 2. You get access on day one You are onboarded onto a task tracking platform where you can follow live development progress and steer which features get built first, and founders and enterprises also get a private group chat between your team and ours. ### 3. We build in four milestones Billed 10% to begin detailed requirements gathering and scoping, 40% to commence the build, 30% at the mid-project milestone that is delivered for your review, and 20% on final handover — each one invoiced when it is signed off, and every line of code reviewed by a human engineer. ### 4. You own what we built On final payment every piece of intellectual property we made for you transfers to you outright, so you are never tied to us to keep using it or to hand it to another developer. ### 5. We stay on afterwards, at a discount If you bring us in at the start of a new product rather than after it is built, the long-term retainer that keeps it running afterwards is discounted. We would rather maintain something we designed than inherit something we did not, and the pricing reflects that — the rate is set out in your proposal alongside the build. ## Frequently asked questions ### How much does a project cost? Offload Foundry does not publish a price list, because the honest answer is that the price follows the scope. After a scoping conversation we send a written quote setting out what we will build, the milestones, and the fee — and that quote holds for 30 days. What we can tell you up front is how the money is structured rather than what it adds up to: four milestones, billed 10% to begin detailed requirements gathering and scoping, 40% to commence the build, 30% at the mid-project milestone and 20% on final handover. Third-party costs such as hosting, domains and paid APIs are billed at cost and are separate from our fees. We are not GST-obliged yet, so no GST is added. One standing offer worth knowing before you decide: if you bring us in at the start of a new product rather than after it is built, the long-term retainer that keeps it running afterwards is discounted. We would rather maintain something we designed than inherit something we did not, and the pricing reflects that. The rate is set out in your proposal alongside the build. ### How long does a project take? Also a function of scope, but the Offload Foundry AI-driven workflow is the reason the answer is usually weeks rather than months. A small senior team moves at the pace of a much larger one, without the quality trade-off — every line of code is still reviewed by a human engineer. Your proposal carries a milestone schedule with dates, not a vague estimate. The most common cause of a slipped date is a project waiting on feedback or access from the client side; when that happens we will tell you at the time that the timeline has moved, rather than absorb it quietly and miss the date later. ### How does payment work, and what happens if we cancel? Payment for an Offload Foundry engagement is milestone-based across four stages: 10% to begin detailed requirements gathering and scoping, 40% to commence the build — which is what reserves your slot in the schedule — 30% when the mid-project milestone is delivered for your review, and 20% on final handover. Each milestone is invoiced when it is signed off, and invoices are due within 14 days. Either of us can end an engagement in writing at any time, and what happens to the money does not depend on who ended it. Milestones we have already delivered are payable and are not refundable. Work in progress on the current milestone is billed for the time actually spent, and anything you paid beyond that comes back to you. Milestones we have not started are not billed, and anything prepaid on them is refunded in full. The full wording is in our Terms of Service. ### Who owns the work once it is finished? You do, outright. All intellectual property in what Offload Foundry builds specifically for you — the code, the designs, the content we produce for you — transfers to you on receipt of final payment. You do not license it from us, and you are not tied to us to keep using it or to hand it to another developer. One carve-out, stated plainly rather than buried: we keep ownership of the general-purpose components and libraries we bring to every project. Where those end up inside your deliverables, you get a perpetual, worldwide, royalty-free licence to use, modify and distribute them as part of your product — the limits are that you cannot resell or sublicense those components on their own, or use them to build a service competing with ours. None of that restricts what you can do with the deliverables we built for you. See section 6 of our Terms. ### Can you help my business adopt AI? Yes. Beyond building products, Offload Foundry helps businesses work out where AI genuinely fits and then make it real. We run workshops and training sessions for your team, from executive briefings on what AI can and cannot do for your industry, to hands-on sessions that get your staff productive with AI tools in their day-to-day work. We also handle the technical side: assessing your current processes for automation opportunities, setting up the infrastructure, integrating AI into your existing systems and data, and putting sensible guardrails around security, privacy, and governance. You end up with a team that knows how to use AI and the setup to support it, rather than a pile of subscriptions nobody uses. The formats, what a workshop day actually covers, and where the funding sits are set out in full on the AI adoption workshops and training page. ### Is SEO included in your services? Yes. Every web application Offload Foundry builds for you ships with SEO and AEO built in as standard, not as a paid add-on. On the SEO side, we build with search engine best practices from day one: fast page loads and strong Core Web Vitals, mobile responsiveness, semantic and accessible markup, clean URL structures, proper metadata and Open Graph tags, XML sitemaps, canonical tags, and server-side rendering so your content is actually crawlable. ### What is AEO, and how do you make it happen? AEO stands for Answer Engine Optimisation, sometimes called AI search optimisation. More and more people now start their search in ChatGPT, Claude, Perplexity, Google AI Overviews, or Copilot instead of a traditional results page. These tools do not show ten blue links, they give one answer and cite a handful of sources. AEO is the work of making sure your business is one of the sources they cite, and that what they say about you is accurate. Concretely, Offload Foundry structures your site so AI systems can read and trust it. That means machine-readable structured data (JSON-LD schema for your organisation, products, services, and FAQs), content organised into clear question-and-answer blocks that map to how people actually ask things, and factual, self-contained sections an AI can quote without losing context. We also handle the crawler side: AI-aware robots.txt rules, an llms.txt file that gives AI agents a clean summary of your site, and server-rendered content so nothing important is hidden behind JavaScript. Combined with consistent business information across your site and third-party profiles, this gives answer engines the corroboration they need to recommend you with confidence. ### I still have unanswered questions! Ask Offload Foundry directly — that is usually faster than guessing which answer above nearly fits. Tell us what you are trying to build and we will tell you whether we are the right people for it. Send us a message or email sales@notify.offloadfoundry.com. We reply within two business days. ## Contact Email sales@notify.offloadfoundry.com, or use the enquiry form at https://offloadfoundry.com/#contact. Required fields are name, email address and message; the mobile number is optional. A human replies within two business days. See https://offloadfoundry.com/agent-permissions.json for what an automated agent may do here. --- # Bespoke web development in Singapore Service: Bespoke web applications (Bespoke web application development). Provider: Offload Foundry, Singapore. Canonical version: https://offloadfoundry.com/services/bespoke-web-development Custom web applications designed and built for how a business actually works, by the engineer who builds them. Milestone-billed, SEO and AEO as standard. ## What "bespoke" means here Offload Foundry is a Singapore-based bespoke web and AI development agency. On this page, bespoke means the application is designed around how your business already works, rather than your business being reshaped to fit what a template or an off-the-shelf platform happens to do. That distinction sounds like marketing until it costs money. A template decides your data model for you. It decides what a "customer" is, what fields an order has, and which of your actual operations are impossible. Most of the expensive rework on a small business system is not the build — it is the six months afterwards spent working around a decision that was made by a theme author who had never heard of your company. The honest counterweight, said before you spend anything: not every project needs this. If your requirement is a five-page brochure site that will not change for three years, a good template is the correct answer and a custom build is you paying for flexibility you will never use. Say that at scoping and you will get a straight answer about it — a project that should not have been bespoke is a bad project for both sides. ## What it is built with, and why that stack Every project listed on this site — the client work and all four of the products this agency builds and runs for itself — is built on the same foundation: React and Next.js, server-rendered, deployed on Vercel. That is not a coincidence and it is not fashion. It is the shape that has the properties a small business actually needs from software it has to live with for years. - Server-rendered, so the content is in the HTML. What your site says about you is present in the first response, before any JavaScript runs. That is what makes it readable by a search crawler, by an AI answer engine, and by someone on a slow connection in a car park. A client-rendered site can be invisible to all three at once and look perfect on your laptop. - No server to keep patched. A static deployment on a managed platform has no database sitting on the public internet, no plugin update to miss and no admin login to be brute-forced. The single most common way a small-business website is compromised is an unmaintained plugin, and the way to not have that problem is to not have plugins. - Typed, reviewed and tested. TypeScript throughout, every line reviewed by a human engineer, and automated checks on every change. AI does a great deal of the work across the delivery cycle — that is why the timeline is what it is — but it does not get the last word on anything that ships. - Accessible and semantic by construction. Real headings, real landmarks, keyboard operability and colour contrast are decided while the interface is being designed, not retrofitted after an audit finds them. If your project genuinely needs something else — a different runtime, an existing system to integrate with, a database with real write traffic — that is a scoping conversation, not a refusal. What will not happen is a stack chosen because it is interesting to build. The question is always what this system has to do for the next five years, and who has to maintain it. ## SEO and AEO ship with the build, not as an add-on Search visibility is a property of how a site is built, and it is close to free at build time and expensive to add later. So it is not a line item. Every build ships with the technical foundations in place: fast page loads and strong Core Web Vitals, mobile responsiveness, semantic and accessible markup, clean URLs, per-page metadata and Open Graph tags, an XML sitemap, canonical tags, and server-side rendering. Answer Engine Optimisation is the same work aimed at a different reader. More people now start a search in ChatGPT, Claude, Perplexity, Google AI Overviews or Copilot, and those tools do not return ten links — they give one answer and cite a few sources. Being one of the cited sources means structured data an engine can parse, content organised as self-contained questions and answers, crawler rules that name the AI agents explicitly, and an llms.txt that hands an agent a clean summary of the site. The site you are reading is the reference implementation, and it is checkable rather than claimed. Fetch /llms.txt or /llms-full.txt and you get this entire site as plain text. Fetch /index.md, /terms.md or /privacy.md for the Markdown twins. View the source of any page for the JSON-LD graph, or read /robots.txt for the per-crawler rules. If a claim on this page is not true of this page, you can find that out in about ten seconds — which is the standard the work is supposed to meet. ## How an engagement runs Four milestones, and you know the shape of the money before you commit to any of it. There is no published price list, because the price follows the scope — but the structure never changes, and it is the same one written into the Terms of Service. - 10% — scoping. Detailed requirements gathering. This produces the written quote: what gets built, the milestone schedule with dates, and the fee. The quote holds for 30 days. - 40% — build commencement. This is what reserves the slot in the schedule. - 30% — mid-project. Delivered for your review, not for your sign-off in principle. You are looking at working software. - 20% — final handover. Intellectual property transfers to you on receipt of this payment. Each milestone is invoiced when it is signed off, and invoices are due within 14 days. Third-party costs — hosting, domains, paid APIs — are billed at cost and are separate. Offload Foundry is not GST-registered, so no GST is added. You will be working with the engineer who builds it, not an account manager relaying messages to a team you never meet. Timelines are usually weeks rather than months, and your proposal carries dates rather than an estimate. The most common cause of a slipped date is a project waiting on feedback or access from the client side; when that happens you will be told at the time that the date has moved, rather than have it absorbed quietly and missed later. Either side can end an engagement in writing at any time, and what happens to the money does not depend on who ended it. Delivered milestones are payable and not refundable; work in progress is billed for time actually spent; milestones not started are refunded in full. The full wording is in the Terms of Service. ## You own what is built for you All intellectual property in what is built specifically for you — the code, the designs, the content produced for you — transfers to you on receipt of final payment. You do not license it back. You are not tied to this agency to keep using it, and handing the repository to another developer is a normal thing to do rather than a breach of something. One carve-out, stated plainly rather than buried in a schedule: the general-purpose components and libraries brought to every project stay owned by Offload Foundry. Where they end up inside your deliverables you get a perpetual, worldwide, royalty-free licence to use, modify and distribute them as part of your product. The only limits are that you cannot resell or sublicense those components on their own, or use them to build a competing agency service. None of that restricts what you can do with the thing that was built for you. It is section 6 of the Terms. ## What there is to check This is a young agency under a new name, and the useful thing to say about evidence is exactly how much of it there is. There is one named client engagement, written up in full: the Lansys Pte Ltd case study covers the design, the copy, the build and the migration of a corporate site for a Singapore network-cabling and IT-infrastructure firm. It states plainly that no before-and-after metric was captured, because none was. The other evidence is the four products on the homepage — OYLIW, Creator Offload, ibuytoto and Tricxter. Those are not client logos. They are products this agency designed, built, operates and pays the bills for, which means the same decisions get made with its own money on the line. You can open them and form your own view, which is more than a testimonial offers. ## Starting a project Tell Offload Foundry what you are trying to build and you will get a straight answer about whether this is the right place for it — including when it is not. Start a project or email sales@notify.offloadfoundry.com. A human replies within two business days. --- # AI adoption workshops and training for Singapore businesses Service: AI adoption workshops and training (AI adoption consulting and staff training). Provider: Offload Foundry, Singapore. Canonical version: https://offloadfoundry.com/services/ai-adoption-workshops Workshops, staff training and the technical groundwork that get a Singapore team genuinely productive with AI — run by an engineer who builds with it daily. ## The problem this actually solves Offload Foundry is a Singapore-based bespoke web and AI development agency. The most common state to find a business in right now is not "we have not started with AI". It is that a handful of subscriptions have been bought, two people are enthusiastic, everyone else has tried a chatbot once, and nobody can say what any of it has changed. That is a predictable outcome of buying tools before deciding what they are for. The gap is rarely the technology, which is more capable than most teams are using it for. It is that nobody has worked out which parts of this specific business AI is genuinely good at, taught the people who do that work how to use it on their actual tasks, or put anything in place about what may and may not be pasted into a third-party model. The point of this service is to close that gap and leave: a team that knows how to use AI on the work they do, and the setup to support it — rather than a pile of subscriptions nobody uses. ## The workshop formats Sessions are shaped around who is in the room, because the useful thing to tell a management team and the useful thing to tell the people doing the work are not the same thing. - Executive briefings. What AI can and cannot currently do for your industry, what it costs, where the risk sits, and how to tell a real use case from an expensive demo. Aimed at the people who have to decide where the budget goes, and deliberately as clear about the limits as about the capabilities. - Hands-on team sessions. Your staff, their real work, in the room. Not a generic prompt-writing course — the useful version of this is bringing the tasks that actually eat your team's week and working through them together, because the productive uses of AI in a business are almost always specific to that business. - Role-specific training. Different functions get value from completely different things. What helps a finance team is not what helps a support team or a sales team, and a single all-hands session tends to be simultaneously too basic and too abstract for everyone in it. - Follow-up. A single workshop is a good way to create enthusiasm that fades in three weeks. What makes it stick is coming back once people have hit real friction with real work. Format, length and mix are set at scoping, and the proposal says what is being delivered and when. There is no standard package to fit your company into. ## The technical side, not just the training Training on its own has a ceiling. Past a certain point the constraint stops being what your staff know and starts being that the AI has no access to your data, or that the workflow it would improve is a manual one nobody has automated. That work is the other half of this service. - Process assessment. Going through how work currently moves through the business and identifying where automation or AI genuinely pays off — which frequently is not where people expect, and sometimes is nowhere, in which case that is what gets said. - Infrastructure. The accounts, access, tooling and cost controls that let a team use AI without every request going through one person's personal subscription. - Integration with your systems and data. AI is far more useful when it can see the business's own information. This is where most of the engineering effort lives, and it is the same engineering discipline as the bespoke web development work. - Guardrails. Security, privacy and governance: what data may go to which provider, what must never leave, what gets logged, and who is accountable for output that goes to a customer. In Singapore this is also a PDPA question, and it is much cheaper to answer before an incident than after one. ## Why take this from a working engineer The AI training market has a large supply of people teaching it and a much smaller supply of people shipping with it. The distinction matters, because the things that actually go wrong — where models are unreliable, where the review step is non-negotiable, what genuinely gets faster and by how much — are learned by building, not by reading about building. AI is built into how this agency delivers every project: requirements, architecture, implementation, testing and documentation, which is why a small senior team ships in weeks rather than months. It is also used on the quality side — generating test coverage, catching regressions, flagging security and accessibility issues. And every line of code is still reviewed by a human engineer, which is itself one of the more useful lessons to pass on. The four products on the homepage were built this way, with this agency's own money paying for the mistakes. That is the evidence behind the training, and it is inspectable. ## Government support, and where Offload Foundry stands on it Singapore has an unusually strong policy push behind enterprise AI adoption, and there are national programmes and co-funding schemes — the Productivity Solutions Grant among them — aimed at helping businesses take it up. It is worth checking what is currently available through IMDA and Enterprise Singapore before you plan a budget, because the schemes and their terms change. The part that gets stated here rather than discovered later: Offload Foundry is not a pre-approved vendor under those schemes, and engagements with it should not be assumed to be claimable. Grant support of that kind runs through a pre-approved supplier listing, which requires ACRA business registration, and Offload Foundry is not a registered legal entity — the same fact the Terms of Service and Privacy Policy are written around. That is a real disadvantage against a listed vendor and it is not worth hiding, because you would find out at the point of claiming. If grant eligibility is decisive for you, a pre-approved vendor is the right choice and that is a reasonable decision to make. If what you want is someone who builds with these tools every day, the funding position is a discount you do not get rather than a reason the work is worse. ## Arranging a session Tell Offload Foundry who would be in the room and what your team is actually trying to get done, and you will get an honest read on whether a workshop helps or whether the problem is somewhere else. Start a conversation or email sales@notify.offloadfoundry.com. A human replies within two business days. --- # Micro-SaaS development in Singapore Service: Micro SaaS and products (Micro-SaaS product design, development and operation). Provider: Offload Foundry, Singapore. Canonical version: https://offloadfoundry.com/services/micro-saas-development Design, build and run a small software product people can pay for — by an agency that builds, operates and pays for four of its own. ## What "micro-SaaS" means here Offload Foundry is a Singapore-based bespoke web and AI development agency. Micro-SaaS is the smaller end of product work: a piece of software that does one job for one clearly-defined audience, that people pay to keep using, and that one person or a small team can run without a department behind it. The distinction that matters is not size, it is what the thing has to survive. A client project is delivered, signed off and handed over. A product has to keep working on a Sunday, keep being paid for, and keep being changed after launch by whoever is left holding it — usually you. That changes what is worth building and what is worth leaving out, and it is the reason product work is on this site as its own service rather than as a website with a login on it. The scope this covers is the whole arc: working out what the smallest version that someone would pay for actually is, designing and building it, getting it live, and — where you want it — staying on to run it. Not every engagement uses all of that. Some stop at the first launch, which is a legitimate place to stop. ## The evidence, and its exact limits The reason this service is on the site is that Offload Foundry does it for itself. Four products are designed, built, operated and paid for by this agency, which means every decision in them was made with its own money on the line rather than a client's: - OYLIW (oyliw.com) — a life calendar that draws a long life as a grid of about 4,680 weeks and fills in the ones already lived. Live. - Creator Offload (creatoroffload.com) — UGC creator management for agencies: briefs, submissions, rights clearance and review as one pipeline, behind a public REST API and signed webhooks. In beta with a founding-partner cohort, not general availability. - ibuytoto (ibuytoto.com) — CPF-aware FIRE calculators for Singapore professionals working out when they can afford to stop. Live. - Tricxter (tricxter.com) — generates realistic-looking but completely invalid gift-card codes, so someone being scammed can waste the scammer’s time instead of their money. Live. You can open all four and form your own view, which is more than a case study offers. What you will not find on this site is a user count, a revenue figure or a growth chart for any of them — not because the numbers are bad, but because a self-reported metric nobody can check is worth nothing to you, and publishing one would undermine every other claim on this site that you can check. The honest gap, stated here rather than discovered at the third meeting: no micro-SaaS has yet been built for a client under this name. The one client engagement on record is a corporate site rebuild and migration — the Lansys case study — which is a different kind of work. The product experience is real and it is first-hand; it is just not yet client experience, and you should price that in when you decide. ## What a product build has to cover that a website does not Most of the cost and nearly all of the risk in a small product sits in the parts nobody demos. They get decided at scoping, in this order, because each one constrains the next: - What the smallest paid version is. The most expensive mistake available here is building the second version first. The useful question at scoping is not what the product could eventually do, it is which single job someone would pay for today — and if the answer to that is unclear, more software is not the fix. - The data model. Everything downstream inherits it. Get it wrong and every later feature is a workaround; this is the same argument as the bespoke web development page makes about templates, and it applies harder to a product, because a product lives longer. - Accounts, access and billing. Who can see what, and how money is collected and stopped. These are not features, they are the shape of the thing. - The operational half. Monitoring, backups, error reporting and running costs. A product that nobody is watching is a product that is down and nobody knows. - An interface for someone else. Where the product is a platform rather than a tool — as Creator Offload is — that means a documented API and webhooks, which is a design commitment made early or paid for later. What is built with, and why, is the same answer as everywhere else on this site: React and Next.js, server-rendered, on managed hosting, typed and human-reviewed, with a Postgres database where there is state to keep. The reasoning behind that stack is set out in full on the bespoke page rather than repeated here. If your product needs something else, that is a scoping conversation rather than a refusal. ## When this is the wrong thing to buy Said before you spend anything, because it is cheaper now than in month four. A product build is the wrong purchase if what you actually have is an idea you have not yet tested on a single person who would pay for it. Software is a slow and expensive way to find out that nobody wants something, and there is usually a faster one — a spreadsheet, a manual service you run by hand for ten customers, a landing page that takes a deposit. It is also the wrong purchase if the thing you want is an internal tool for your own staff, because that is a different economic argument: it does not need billing, it does not need to survive strangers, and it is usually smaller. That is still work this agency does — it just should not be scoped as a product. Say what you are trying to do and you will get a straight answer about which of the three you are looking at. A project scoped as the wrong thing is a bad project for both sides. ## How it is billed, and who owns it The same four milestones as every other engagement — 10% for detailed requirements gathering and scoping, 40% to commence the build, 30% at the mid-project milestone delivered for your review, 20% on final handover — with the fee fixed in a written quote before you commit to any of it. There is no price list; how pricing works sets out the structure, what moves a quote, and what is deliberately not published. Intellectual property in what is built for you transfers to you on final payment, with one carve-out for the general-purpose components brought to every project, which you get a perpetual royalty-free licence to use inside your product. For a product this matters more than usual: it is the difference between owning an asset and renting one. The full wording is section 6 of the Terms. One standing offer that applies to this service more than any other: 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. The reasoning is not generosity — maintaining something designed here is genuinely cheaper than inheriting something that was not, and the pricing reflects that. The rate is set out in your proposal alongside the build. ## Starting a product Describe the job your product would do and who would pay for it, and you will get an honest read on whether it is worth building yet. Start a project or email sales@notify.offloadfoundry.com. A human replies within two business days. --- # Web development pricing in Singapore, without a price list Last updated: 2026-08-09. Canonical version: https://offloadfoundry.com/pricing No price list, and the reason why. How a quote is produced, what moves it, the four-milestone payment structure, and what happens if you cancel. ## Why there is no price list on this page 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. ## How you get to a fixed number 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. ## The four-milestone structure 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. ## What actually moves a quote 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 and /robots.txt are the two fastest ways to check whether that claim is true. ## If the project stops 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. ## What it costs to keep it running 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. ## What this page deliberately does not tell you 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. ## Getting a number 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. --- # About Offload Foundry Last updated: 2026-08-09. Canonical version: https://offloadfoundry.com/about Singapore bespoke web and AI development agency, run by Chun Mun Loh. Formerly Web Dev Solutions. What it builds, and what it does not claim. ## What Offload Foundry is Offload Foundry is a Singapore-based bespoke web and AI development agency. It builds custom web applications and micro-SaaS products for solopreneurs, founders and enterprises, and it helps businesses adopt AI through workshops, staff training and the infrastructure to support it. It is a small operation, deliberately. The work that comes out of it is bespoke web development and AI adoption workshops and training, and the same person scopes, designs, builds and hands over. There is no account manager between you and the engineer, because there is no one to be an account manager. ## Who runs it Chun Mun Loh, Founding Engineer — founder, sole point of contact, and the person who writes the code. Public profiles: GitHub and LinkedIn. The most useful thing to point at is not a biography, it is a body of work that can be opened. Four products — OYLIW, Creator Offload, ibuytoto and Tricxter — were designed, built and are operated and paid for by this agency rather than by a client. They are listed with their stacks on the homepage, and they are the reason the claims made elsewhere on this site about delivery speed and quality are checkable rather than asserted: the same decisions were made with this agency's own money at stake. On the client side there is one named engagement, and it is written up rather than reduced to a logo: the Lansys Pte Ltd case study. It is also candid about what was not measured, which is the standard the rest of this site is meant to hold to. ## Formerly Web Dev Solutions Offload Foundry was previously known as Web Dev Solutions, at webdevsolutions.io. The name changed in 2026. Same founder, Chun Mun Loh; same Singapore agency; same work. Only the name and the domain changed — Offload Foundry and Web Dev Solutions are the same business. If you are holding a link, an invoice, an email address or a business card that says Web Dev Solutions, it refers to this agency. The current address is offloadfoundry.com. ## What this agency does not claim Most of what damages trust in this industry is small overstatement, so the position is set out plainly rather than left to be discovered. - Not a registered company. Offload Foundry is not an incorporated legal entity and holds no ACRA registration or UEN. That is stated the same way in the Terms of Service and the Privacy Policy, and it is why no registration number, company type or founding date appears in this site's structured data — a claim in machine-readable form is still a claim. - Not GST-registered. No GST is added to any invoice. - No office to visit. There is no published street address, because there is no premises a client would come to. The agency works with clients in Singapore and is contacted by email or through the form on this site. - One named client, not a wall of logos. There is exactly one client engagement published, and it is published in full. Any impression of scale beyond that would be manufactured. - No published prices, and no invented results. The price follows the scope and arrives as a written quote. No before-and-after metric appears anywhere on this site, because none was captured — the case study says so in its own words. None of that is an apology. It is the information you would want before engaging a small agency, and a firm that will tell you the unflattering half up front is usually the one that will tell you when a date has slipped. ## What working with it looks like A scoping conversation first, then a written quote setting out what gets built, the milestone schedule with dates, and the fee. The quote holds for 30 days. Billing runs across four milestones — 10% for scoping, 40% to commence the build, 30% at mid-project review, 20% on handover — and invoices are due within 14 days. Everything built specifically for you transfers to you on final payment: the code, the designs, the content. You are not licensing your own product back, and you are free to hand it to another developer. The one carve-out, for the general-purpose components brought to every project, is section 6 of the Terms. Enquiries get a human reply within two business days. Start a project, or email sales@notify.offloadfoundry.com. --- # Rebuilding and migrating the Lansys corporate site Client: Lansys Pte Ltd (https://lansys.com.sg). Year: 2024. Scope: Design, Build, Migration, Content. Stack: Next.js, React, Vercel. Canonical version: https://offloadfoundry.com/work/lansys How Offload Foundry designed, wrote and migrated the corporate site for Lansys Pte Ltd, a Singapore network-cabling and IT-infrastructure firm. ## The client Lansys Pte Ltd is a Singapore firm working in structured network cabling and IT infrastructure — the physical and network layer that offices, data rooms and industrial sites run on. Their buyers are facilities managers, IT managers and main contractors, and the purchase is a considered one: a prospect wants to establish that the firm is real, established, and has done work at their scale before they pick up the phone. That makes the corporate site a credibility instrument rather than a storefront. It has no cart, no login and no funnel. Its entire job is to answer "are these the right people for this job" and then make it easy to ask. ## The engagement The engagement covered four things, which are the four scope tags on the card that links here: design, build, content and migration. Offload Foundry was responsible for all four — there was no separate agency holding the design or the copy, which is the arrangement that usually causes a site like this to stall. - Design. A layout and visual system for a services firm whose differentiator is competence rather than novelty. Legible, conventional where convention helps a buyer, and built to survive a page being added later. - Content. The site copy was written as part of the engagement rather than supplied. Services firms usually have the knowledge and no time to write it down; the practical route is to interview and draft, then have the client correct the technical detail. - Build. Next.js and React, deployed on Vercel. Server-rendered, so the content is in the HTML for a crawler rather than assembled by JavaScript after load. - Migration. Moving the existing site to the new one without losing the addresses people and search engines already had for it. ## How it was built The stack was chosen for what the site has to do for the next five years, not for what is interesting to build. A corporate site for a services firm is edited a few times a year, gets read on a phone in a car park, and must not require its owner to keep a server patched. Next.js on Vercel makes it a set of static pages with a deployment pipeline behind them, which is the lowest-maintenance shape available for that profile. Server-side rendering is the part that matters beyond convenience. Everything a buyer or a crawler needs — what the firm does, where it operates, how to contact it — is present in the HTML of the first response. That is the same principle behind every build Offload Foundry ships, and the reason SEO is treated as a property of the build rather than as a service sold afterwards. ## The migration, and what it protects The riskiest part of replacing a site that already exists is not the build, it is the addresses. A firm that has been operating for years has its URLs in supplier directories, in tender documents, in email signatures and in a search index. Replacing the site without mapping those addresses to their new locations discards that quietly, and the loss shows up months later as enquiries that stopped arriving. So the migration was treated as its own piece of work: enumerate what exists, decide where each address lands on the new site, and redirect rather than delete. That is unglamorous and it is the single highest-value hour on a project like this one. ## What was and was not measured What can be verified is the site itself: it is live at lansys.com.sg, it was designed, written, built and migrated in this engagement, and it shipped in 2024. What cannot be claimed is a number. No pre-migration baseline was captured — no traffic figure, no Core Web Vitals reading, no enquiry count — so there is no honest before-and-after to publish, and inventing one is not on the table. This is stated plainly here for the same reason the landing page shows one client rather than a wall of logos: a claim that cannot be checked is worth less than an admission that can. On engagements since, a baseline is captured before anything is replaced, precisely so this section can carry a measurement next time. ## Working with Offload Foundry Offload Foundry is a Singapore-based bespoke web and AI development agency. If you have a site that has stopped representing the business, or one that needs replacing without losing what it has accumulated, start a project or email sales@notify.offloadfoundry.com. We reply within two business days. --- # Terms of Service Last updated: 2026-08-08. Canonical version: https://offloadfoundry.com/terms The terms we work under. Written to be read, not to be survived — if anything here is unclear, ask before you sign anything. ## 1. Who these terms cover These terms apply to your use of offloadfoundry.com and to any development, consulting or training work Offload Foundry carries out for you. Where we sign a separate written agreement, proposal or statement of work with you, that document governs the engagement and these terms fill in anything it does not cover. ## 2. What we do We design and build bespoke websites, web applications and micro SaaS products, and we help businesses adopt AI through workshops, training and the supporting infrastructure. What we will deliver on a given engagement is whatever the accepted proposal says we will deliver, and nothing on this website is itself an offer or a fixed price. ## 3. Quotes, scope and changes We quote per project after a scoping discussion, because the price of the work depends on what the work is. A quote sets out the scope, the milestones and the fee, and it is valid for 30 days unless it says otherwise. Work outside the agreed scope is a change request. We will tell you what it costs and what it does to the timeline before we start it, and we will not bill you for scope you did not agree to. ## 4. Fees and payment Engagements are billed against four milestones, each invoiced when that milestone is reached and signed off: - 10% on engagement — payable before we begin detailed requirements gathering and scoping, which is the phase that produces the specification the rest of the work is built against. - 40% on commencement — payable before build work begins, and what reserves your slot in the schedule. - 30% at the mid-project milestone — payable when the milestone named in the proposal is delivered for your review. - 20% on delivery — payable on final handover, before the work goes live under your control. 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 our fees. Offload Foundry is not GST-registered, so no GST is charged on our invoices. ## 5. Refunds and cancellation Either of us may end an engagement in writing at any time. What happens to the money is simple and does not depend on who ended it: - Milestones we have 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 you have paid beyond that is refunded to you. - Milestones we have not started are not billed, and anything prepaid is refunded. We will hand over the work completed to the point of cancellation once the amounts above are settled. ## 6. Who owns the work When the final invoice is paid, you own the work. All intellectual property rights in the deliverables built specifically for you — the code, the designs, the content we produce for you — transfer to you outright on receipt of final payment. You do not license it from us and you are not tied to us to keep using it. One carve-out, stated plainly: we retain ownership of the general-purpose components, libraries and tooling we bring to the project and reuse across clients. Where any of those are embedded in your deliverables, you get a perpetual, worldwide, royalty-free licence to use, modify and distribute them as part of your product. That licence comes with four limits: - you may not extract those components and sell, license or publish them on their own, separately from your product; - you may not sublicense them to anyone else as a licence in their own right; - you may not use them to build or operate a web or AI development service that competes with ours; and - the licence ends if you breach these terms — including the payment terms in §4 — and is not restored by a later payment unless we say so in writing. None of that restricts what you can do with the deliverables we built specifically for you. You own those outright, and the limits above apply only to our reusable components where they happen to sit inside them. Until final payment is received, the deliverables remain ours. We may show completed work in our portfolio; if you would rather we did not, tell us and we will not. ## 7. What we need from you Projects slip when they are waiting on someone, so this is a real obligation and not boilerplate. You agree to provide the content, brand assets, accounts and system access the work depends on, and to give feedback and sign-off within the timeframes set in the proposal. You confirm that anything you give us — content, imagery, data — is yours to give. Where a delay is caused by waiting on you, the timeline moves by at least that much, and we will say so at the time rather than absorb it silently. ## 8. Confidentiality Anything you tell us about your business in the course of an engagement is confidential. We will not disclose it, and we will not use it for anything other than doing your work. The same applies in reverse to what we tell you about how we work. Personal data is handled as described in our Privacy Policy. ## 9. Warranty We warrant that the work will be carried out with reasonable skill and care, and that deliverables will substantially match the accepted scope. If something we built is broken on delivery, tell us within 30 days of handover and we will fix it at no charge. That warranty does not cover changes made by you or a third party after handover, faults in third-party services or platforms outside our control, or new work that was not in the agreed scope. ## 10. Limitation of liability Neither of us is liable to the other for indirect or consequential loss, including lost profits, lost revenue or lost data. Our total liability arising out of an engagement is limited to the fees you have paid us for that engagement. Nothing in these terms limits liability that cannot lawfully be limited, including liability for fraud or for death or personal injury caused by negligence. ## 11. Governing law These terms are governed by the laws of Singapore, and the courts of Singapore have exclusive jurisdiction over any dispute arising from them. ## 12. Changes and contact We may update these terms. The version that applies to your engagement is the one in force when your proposal was accepted, and the date at the top of this page is when the current version took effect. Questions go to sales@notify.offloadfoundry.com. We reply to enquiries within two business days. --- # Privacy Policy Last updated: 2026-08-09. Canonical version: https://offloadfoundry.com/privacy What Offload Foundry collects when you use this site, why we collect it, where it goes, and how long we keep it. ## Who this policy covers Offload Foundry is a Singapore-based web and AI development practice operating the website at offloadfoundry.com. This policy applies to that website and to enquiries submitted through it. It is written to be read alongside Singapore's Personal Data Protection Act 2012 (PDPA). ## What we collect We collect only what the site actually asks for, plus anonymous measurements of how the site itself performs. There is no advertising pixel on this site, nothing here follows you to other websites, and none of it sets a tracking cookie. - Enquiry details. When you submit the contact form we collect your name, email address, the message you write, and — only if you choose to give it — your mobile number. The mobile number is the one optional field; the other three are required, and nothing else is captured from that form. - Your IP address. The contact form is rate-limited to stop it being used to send bulk messages. To do that, the server reads the IP address your request arrives from and counts recent submissions against it. That count is held in the server's memory only — it is never written to a database, and it is lost whenever the server restarts. - Anonymous usage and performance measurements. We use our hosting provider's built-in web analytics and page-speed measurement to see which pages are visited, roughly where visitors come from, and how quickly pages load. These are cookieless: they set nothing on your device and store no identifier that persists across days, so they cannot be used to recognise you on a return visit or to follow you to another site. We see counts and page-speed figures, not people. - Hosting logs. Our hosting provider keeps standard request logs (IP address, timestamp, requested URL, user agent) as part of running the service. We do not use those logs for marketing or profiling. - Your theme choice. If you switch between the light and dark theme, that choice is stored in your own browser under the key of-theme. It never leaves your device, it is not a cookie, and it identifies nobody. ## Why we collect it Enquiry details are collected for one purpose: so that we can reply to you and discuss the work you are asking about. Your IP address is collected for one purpose: preventing abuse of the contact form. The usage and performance measurements are collected for one purpose: keeping this site fast and working out which pages are worth improving. We do not use any of it to build a profile of you, and we do not send marketing to people who have only ever sent us an enquiry. By submitting the contact form you consent to us using your details for that purpose. You may withdraw that consent at any time — see Your rights below. ## Where your enquiry goes When you submit the contact form, the fields you filled in are sent to our server, and our server immediately forwards them to our internal inbox. That is how we are notified that you have written to us, and it is the only reason the form exists. We use third-party messaging and hosting services to receive and store enquiries, and some of those services run on servers outside Singapore. Your name, email address, message and — where you gave one — your mobile number therefore leave Singapore, and are held by those providers under their own terms and privacy policies. The receiving inbox is private, and access is limited to the people who need to read enquiries in order to answer them. Aside from those service providers, we do not disclose your personal data to anyone. We do not sell it, rent it, or share it with advertisers or data brokers. ## How long we keep it - Enquiries. Your enquiry stays in our inbox for as long as we may reasonably need it to deal with your enquiry and any work that follows from it. We do not run a scheduled purge, so we are not going to promise you a deletion date we would not meet. What we will do is delete it whenever you ask us to — see Your rights below — and we do not keep enquiry data for any purpose beyond the one stated above. - Rate-limit records. The in-memory count tied to your IP address expires 20 hours after it is created, and is discarded entirely whenever the server restarts. Nothing about it is retained. - Usage and performance measurements. Retained by our hosting provider in aggregate form for their standard reporting window, which we do not extend. There is nothing in them tied to you to delete. - Hosting logs. Retained by our hosting provider for their standard log-retention period, which we do not extend. ## How we protect it The site is served over HTTPS, so what you type into the form is encrypted in transit. The webhook that delivers your enquiry is held as a server-side secret and is never exposed to your browser. Access to the receiving channel is restricted. No system is perfect, and we do not claim any certification or attestation we do not hold. ## Your rights Under the PDPA you may ask us to: - tell you what personal data of yours we hold and how it has been used; - correct anything that is wrong or incomplete; - delete your enquiry and the personal data in it; or - stop using your data — that is, withdraw the consent you gave when you submitted it. Email sales@notify.offloadfoundry.com and we will respond within 30 days, as the PDPA requires. Withdrawing consent means we can no longer contact you about your enquiry, so it will normally end the conversation. ## Data protection contact Questions, requests and complaints about how we handle personal data go to sales@notify.offloadfoundry.com. If you are not satisfied with our response, you may raise the matter with the Personal Data Protection Commission of Singapore. ## Changes to this policy If we change how we handle personal data — for example, if enquiries start reaching us through a different service — we will update this page and change the date at the top of it. The date at the top is always the date the current version took effect. See also our Terms of Service.