# The author writes he built gethowmuch.net, a set of finance calculators for Singaporeans covering mortgages, retirement and savings, entirely with Muse - a launch post with no revenue claims

Meta Muse · X (Twitter) · No revenue or traffic is mentioned; the post is a launch share with no monetisation information.

## Business summary

Marcus, who says he is a Meta employee, writes that he built gethowmuch.net, a set of finance calculators for Singaporeans covering mortgages, retirement, savings and other adulting decisions, entirely with Muse, attaching the URL. The post is a public reply to @MattPRD and names @Muse in its text. This is a launch share: the post gives no stack, no build time, no full feature list, no traffic data and no revenue or monetisation information. That the site exists and was built is supported by the URL and the author's account, but the build-process details are not given. The author's identity (Meta employee) is self-described and not verified; this is not a vendor story - he is sharing a product he built in a personal capacity.

## Business value

What has changed for niche tool sites is that the barrier moved from front-end engineering to requirements and correctness: what to compute, which parameters, whether the formula is right. Giving the implementation to an agent while the person owns the definitions and the verification is a workable path. Two cautions: financial formulas must be checked against a known reference before launch, and a built site says nothing about usage - the post gives no traffic or revenue data, and launching is not earning.

## Workflow

Turn the audience into a requirements sheet: who the calculators are for, the list of calculators (mortgage, retirement, savings and more), each one's inputs and outputs, and the source of every financial assumption. Missing assumptions are asked, never invented.

Implement the calculators one by one: input form, calculation logic, result display and an out-of-scope notice where inputs fall outside the model's validity.

Give each calculator a demo input with its expected output, plus verification cases: the same inputs run through a public authoritative calculator.

Verify case by case; anything off by more than the agreed tolerance (say 1%) stops and gets fixed, and unverified calculators are marked not shippable.

Assemble the site: navigation, an explainer per calculator and a disclaimer (not financial advice); output the site structure and a deploy note - deployment itself stays with me.

Hand me a pre-launch checklist: verification status per calculator, demo inputs and outputs, and open items.

## Preparation and limitations

The post gives no stack, no build time, no full feature list, no traffic data and no revenue or monetisation information. The author's identity (Meta employee) is self-described and not verified. AgentFlow did not visit any site backend and verified no traffic or revenue.

## Starter prompt

````text
You are my calculator-site builder. You implement the pages and the calculation logic and assemble the site; the definitions, the formula sign-off and the launch are mine.

INPUT - WHAT I WILL PROVIDE
1) The audience and region (for example: finance decisions for Singaporeans - mortgages, retirement, savings).
2) The calculator list: for each one, its name, inputs and outputs.
3) The formula sources and assumptions (rate assumptions, local rules), or an instruction to follow a named public authority and cite it.
4) Site structure preferences (navigation, explainer pages, disclaimer).

EXECUTION STEPS
1. Restate the requirements sheet: one line per calculator (name / inputs / outputs / assumption source); ask about anything missing rather than assuming financial parameters.
2. Implement each calculator: input form, logic, result display, and an out-of-scope notice where inputs leave the model's validity.
3. Give each calculator a demo input and expected output, plus verification cases: the same inputs run through a public authoritative calculator.
4. Verify case by case; any deviation beyond the agreed tolerance (say 1%) stops and gets fixed, then re-verified. Calculators that fail are marked not shippable.
5. Assemble the site: navigation, an explainer per page and a disclaimer (not financial advice); output the site structure and a deploy note. Deployment stays with me.
6. Before launch, hand me a checklist: verification status per calculator, demo inputs and outputs, and open items.

OUTPUT FORMAT
- Requirements restatement: calculator / inputs / outputs / source
- Per calculator: implementation notes / demo input / expected output
- Verification table: calculator / test input / our output / reference output / deviation / status
- Site structure and deploy note
- Disclaimer copy (not financial advice)
- Launch checklist: item / status

HUMAN CONFIRMATION
The financial assumptions and the tolerance are mine to confirm; domain, deployment and launch are mine to operate. You never mark an unverified calculator shippable, never promise returns or give advice on any page, and the disclaimer is always included.

FAILURE AND MISSING DATA
When a formula source is missing, list candidates from public authorities and wait for my choice - never assume. If a reference calculator is unreachable, record could not verify with the time and retry the same source at most twice. Where authorities disagree, list the differences and let me choose.
````

## Costs and pitfalls

The post gives no stack, no build time, no full feature list, no traffic data and no revenue or monetisation information. The author's identity (Meta employee) is self-described and not verified. AgentFlow did not visit any site backend and verified no traffic or revenue.

## Source and attribution

Marcus (@marcustayye)
https://x.com/marcustayye/status/2099812251695993132
2026-09-15
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
