SaaS development cost calculator. Start with measured builds.

Free, no sign-up. Editing and exports happen in your browser. Public source data is read from the existing site. Your worksheet and company details are not uploaded to a processing API. Analytics record only the tool and action.

Pages, tables, API route files and migrations are measured from each product's build record on Inside. Prices come from the catalog, with its update date. Distinctive capabilities are mapped from published features using reviewed keyword rules; platform capabilities are inherited from SaaSCode Base. The hourly rate, the effort range and the developer-month come from the public sources linked next to each field.

Size is screens and tables. Each page counts as an average IFPUG external output (5 function points), each table as an average internal logical file (10) and each integration you add as an average external interface file (7). API route files add nothing of their own: they implement the functions on those screens, so counting them as well would count the same function twice. Function points times the low and high hours per function point give a range of hours; hours times the hourly rate give dollars, and hours divided by 173.3 give developer-months. Results are rounded to two significant figures.

From scratch counts every page and table of the product. On a starter kit subtracts what the base already ships: sign-in and roles, subscriptions and payments, admin, languages and API keys. Each catalog product copied the base as it was when its build started, so the calculator subtracts that version, counted in the base's history the same way as the build. What remains is never set below a tenth of the product's own count; that floor is a stated assumption, not a sourced figure.

The default rate is the median wage of US software developers, $135,980 a year in May 2025 (US Bureau of Labor Statistics), divided by the 2,080-hour year BLS uses: $65.38 an hour. It is a salaried wage, so agencies and freelancers bill above it. The effort range is the 20th to 80th percentile delivery rate of 1,921 Java and .NET projects in ISBSG's 2021 data: 4.5 to 17.1 hours per function point, median 8.3. The paper prints deciles rather than quartiles, and that band contains the middle half. Replace any of them with your own figures.

On open, it is the build closest to the catalog's median page count, then table count. Capabilities included in every catalog product do not score. When you select distinctive capabilities, builds are ranked by how many they match, then by the selected category, then by closeness to the median size. Products with zero distinctive matches are excluded; if none match, build it to order.

No. It is an order-of-magnitude range from public averages, sized on an existing build. A quote for your scope requires scoping with the factory. The catalog price buys an existing product under its Standard license; checkout determines the final purchase price.

It reads Not measured rather than zero, and the estimate names the missing count instead of guessing it. Build records do not count integrations, so that field starts empty and adds nothing until you fill it. A build whose start date is not recorded uses the oldest measured base, and says so. Data refreshes within ten minutes.