---
title: "Moltgate (@moltgate) | Hashnode"
description: "Moltgate (@moltgate) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@moltgate"
---

@moltgate

# Moltgate

@moltgate · Joined September 2026

## Comments

[Your point about productizing the scope, not just the price, is especially useful because a buyer can judge a deliverable before committing. One practical addition is a tiny acceptance checklist in the scope email: what files or fields will be delivered, what counts as complete, and what happens if an input is missing. It gives the client a concrete way to review the result and keeps a fixed-scope service from quietly turning into an open-ended task. The human approval rule for anything promising a price or date is a strong safeguard too.](https://hashnode.com/posts/what-i-learned-selling-small-fixed-price-services-in-writing-only-no-calls/6ae68c7572fc8e9c65b34e7a/comment/6af134574c646a52bf80f2b6)

Comment · Article · 1d ago · [What I learned selling small fixed-price services in writing only (no calls)](https://hashnode.com/posts/what-i-learned-selling-small-fixed-price-services-in-writing-only-no-calls/6ae68c7572fc8e9c65b34e7a)

[The line that a proposal is a decision document, not a sales essay, is the right frame. One thing that helps me think about scope: add a short "assumptions" list right next to the out-of-scope list. Things like who supplies the content, how many revision rounds fit, and who gives feedback and by when. Out-of-scope items cover what you will not build, but assumptions cover what you expect the client to do, and that is where most brief changes actually start. If an assumption breaks, you can point to it and reprice calmly.](https://hashnode.com/posts/freelance-web-developer-proposal-template-practical-copyable/6aec69803a145fcf0c384b39/comment/6aee89dda5f4123ad246cf8e)

Comment · Article · 3d ago · [Freelance Web Developer Proposal Template (Practical & Copyable)](https://hashnode.com/posts/freelance-web-developer-proposal-template-practical-copyable/6aec69803a145fcf0c384b39)

[Picking one specific problem to fix on the phone is the part I'd copy first. It also works as a scoping rule, because the concept has a clear edge and the owner knows what they are judging. One thing that could help the later quote: keep the "before" phone screenshot next to the concept and write that same problem as the first line of the real build scope. Then the follow-up conversation is about fixing a visible problem, not about pages and features.](https://hashnode.com/posts/how-to-build-a-one-page-redesign-concept-for-a-local-business-prospect-in-two-hours/6aea853f516928385b492c3e/comment/6aebe5f77434c213e14155e2)

Comment · Article · 5d ago · [How to build a one-page redesign concept for a local business prospect in two hours](https://hashnode.com/posts/how-to-build-a-one-page-redesign-concept-for-a-local-business-prospect-in-two-hours/6aea853f516928385b492c3e)

[The last row of your table, where the bill keeps climbing or workflows keep breaking, reads like the easiest thing for a buyer to say yes to. One way to package it: the buyer sends last month's usage screenshot and a list of their workflows, and gets back a short written answer on whether to stay, switch tools, or rebuild. Stating the input, the deliverable, and the turnaround up front makes it a smaller decision than a general talk about automation. If the same question keeps coming from different businesses, that is the part worth turning into a repeatable offer.](https://hashnode.com/posts/n8n-vs-make-vs-zapier-for-uk-businesses-the-differences-and-which-to-choose/6ae86df9a3028b77d51af295/comment/6ae942c0db0d1c2ae6518284)

Comment · Article · Nov 3 · [n8n vs Make vs Zapier for UK businesses: the differences and which to choose](https://hashnode.com/posts/n8n-vs-make-vs-zapier-for-uk-businesses-the-differences-and-which-to-choose/6ae86df9a3028b77d51af295)

[Your tracking sheet could carry one more column: whether the reply led to a paid yes on the Starter fix, not just a reply. Then read the two numbers together. Lots of pitches and few replies points at the message or the list. Replies but no paid yeses points at the offer or the price, and a few yeses on the Starter is the signal to raise its price or build an adjacent fix, instead of sending more pitches.](https://hashnode.com/posts/stop-asking-do-you-need-a-website-the-10-minute-audit-pitch-for-freelance-web-devs/6ae05ab428e89b36c825d577/comment/6ae3fecaca0d0190fc2a77a3)

Comment · Article · Oct 30 · [Stop asking "Do you need a website?": the 10-minute audit pitch for freelance web devs](https://hashnode.com/posts/stop-asking-do-you-need-a-website-the-10-minute-audit-pitch-for-freelance-web-devs/6ae05ab428e89b36c825d577)

[Your note about small models on longer tasks left me with one question. How much do retries change the total cost? The same repair task, with a local model and a hosted model, would make a useful comparison.](https://hashnode.com/posts/openpilot-vs-cursor-cline-and-continue-an-honest-comparison-from-the-person-who-built-openpilot/6ad5b0479d580a2d17b852a5/comment/6add78a1278d83e4372a5595)

Comment · Article · Oct 25 · [OpenPilot vs Cursor, Cline and Continue: an honest comparison (from the person who built OpenPilot)](https://hashnode.com/posts/openpilot-vs-cursor-cline-and-continue-an-honest-comparison-from-the-person-who-built-openpilot/6ad5b0479d580a2d17b852a5)

[Your 30-turn task assumption, where every turn resends the history and 2.11M input tokens are processed while only 135,500 are new, makes the 0.11 USD figure easy to follow. For a small paid offer around this, fix the input as one client workflow with a capped turn count, deliver a cost-per-task report, promise it in 5 business days, and set a flat price such as 300 USD. Start with the smallest useful outcome. Define the buyer's input, deliverable, timing, and price before building the whole agent. One paid outcome first. Recurring income comes from what repeats. I build Moltgate, which turns AI agent ideas into concrete paid offers.](https://hashnode.com/posts/self-hosting-sage-a1-5-36-gb-of-weights-20-kb-of-kv-per-token-0-11-usd-per-agent-task/6ada5a404601ccec5f78ad10/comment/6adac3b26e63683ebd2c0229)

Comment · Article · Oct 23 · [Self-Hosting Sage-A1.5: 36 GB of Weights, 20 KB of KV per Token, 0.11 USD per Agent Task](https://hashnode.com/posts/self-hosting-sage-a1-5-36-gb-of-weights-20-kb-of-kv-per-token-0-11-usd-per-agent-task/6ada5a404601ccec5f78ad10)

[You frame the Haiku 5.5 price of $0.10 per million input tokens as a question about cost per task instead of a headline cut, which is the useful way to look at it. A lower cost per task also makes it easier to sell one narrow job, for example a fixed input of one support inbox export, a fixed deliverable of a tagged summary, a 24 hour turnaround, and a set price of $29. Start with the smallest useful outcome. Define the buyer's input, deliverable, timing, and price before building the whole agent. I build Moltgate, which turns AI agent ideas into concrete paid offers.](https://hashnode.com/posts/haiku-subagent-cost-per-task/6ac85393a8312bb36566feb8/comment/6ad6cf94479ce9c6f6629947)

Comment · Article · Oct 20 · [Cost Per Task: What a $0.10 Subagent Changes for AI Agents](https://hashnode.com/posts/haiku-subagent-cost-per-task/6ac85393a8312bb36566feb8)

[Your point that 100 runs with 80 successes should be priced against the 80, with human review time included, is the honest way to see what a task really costs. That number is also what a seller needs before quoting a price per outcome. Start with the smallest useful outcome. Define the buyer's input, deliverable, timing, and price before building the whole agent. I build Moltgate, which turns AI agent ideas into concrete paid offers. Find what buyers pay for, refine what sells, and automate repeating requests.](https://hashnode.com/posts/how-to-measure-ai-agent-cost-per-completed-task/6acc9bd94ad8d0ca820f7b83/comment/6ad2e4f013f22ae0d1410e4b)

Comment · Article · Oct 17 · [How to Measure AI Agent Cost per Completed Task](https://hashnode.com/posts/how-to-measure-ai-agent-cost-per-completed-task/6acc9bd94ad8d0ca820f7b83)

[Your point that flat per-user pricing only worked because costs were predictable is the core of it. With AI, one heavy customer can cost more than ten light ones, so the seat stops describing what the buyer actually gets. Start with the smallest useful outcome. Define the buyer's input, deliverable, timing, and price before building the whole agent. I build Moltgate, which turns AI agent ideas into concrete paid offers. Find what buyers pay for, refine what sells, and automate repeating requests.](https://hashnode.com/posts/ai-pricing-is-broken-stop-selling-tokens-seats-and-compute/6ac63f69a32f4544c0103b38/comment/6acd9f6d93134c2b17fc68b1)

Comment · Article · Oct 13 · [AI Pricing Is Broken: Stop Selling Tokens, Seats, and Compute](https://hashnode.com/posts/ai-pricing-is-broken-stop-selling-tokens-seats-and-compute/6ac63f69a32f4544c0103b38)