Original Summary

I've been building Handmetric ( https://handmetric.com ). A small business describes a manual process in plain words (invoicing, bank reconciliation, onboarding a customer) and gets back the steps, what it costs per year, how much of it could be automated, the risk involved, and a proposal for how to automate it. The part I care most about is being honest about the numbers: - Every figure is an estimate and says so: about €3,700 a year, somewhere between €1,800 and €5,700, with how confident it is, why, and the exact calculation underneath (624 cases a year × 15 min × €24/h = €3,744). - If a piece of data is missing, there is no number. It tells you what's missing instead of guessing. That rule lives in the database, not only in the UI: CHECK constraints make it impossible to store a figure without a confidence level, or a "can't estimate" without a reason. - The figures don't come from the AI. The AI turns the description into steps and drafts the automation proposal; costs and scores come from fixed rules over your data. Free tools, no sign-up, nothing stored: a process cost calculator, the real cost of an employee (Spanish payroll), what a meeting costs, and "is it worth automating?", which tells you the month it pays for itself. Pricing: 3 processes free, then €29/month + VAT. Stck, for the curious: FastAPI with server-rendered Jinja templates and very little JavaScript, PostgreSQL with row-level security per customer, Redis, and WeasyPrint for the PDF report. Spanish and English. Two things I'd love your take on: Does "about €X, between Y and Z" make you trust a number more or less than a single exact figure? What would you need to see before paying for something like this?   submitted by   /u/VastStorage4125 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/26 23:51:39