Punfyre

Punfyre Forge

How hours translate to cost

Every module is scored across three engineering dimensions (Scope, Depth, and Footprint), each rated on a five-point scale from Standard to Complex. Those scores determine the days estimated for each module, which drive both the integration fee and the ongoing monthly hosting cost.

Estimation dimensions

These appear as colored dots next to each module. They rate each module across three dimensions on a five-point scale.

Scope

How much functionality is included: screens, logic, data, and features. A wider scope means more code to build, review, and maintain.

Depth

Engineering rigor underneath the surface: tests, error handling, security, and compliance. Higher depth reflects more thorough, resilient engineering.

Footprint

How much of the platform this bundle touches: shared data, connected services, and cross-application dependencies that increase coordination cost.

Complexity bands

Five complexity bands that anchor how modules are priced. The dimension bars cycle through valid combinations within each band, illustrating that minor differences in scope, depth, or footprint can exist without shifting the overall cost category.

Standard

Small focused bundle with a handful of screens, straightforward logic, and minimal integrations.

Scope
Depth
Footprint

8–€16/mo

Moderate

Mid-size feature with some backend work and a couple of external connections.

Scope
Depth
Footprint

18–€32/mo

Extended

Multi-screen module with solid test coverage and several shared data models.

Scope
Depth
Footprint

35–€58/mo

Advanced

Complex feature set touching many platform parts, with deep security requirements.

Scope
Depth
Footprint

62–€95/mo

Complex

Full-featured bundle with advanced automation, real-time systems, and compliance requirements.

Scope
Depth
Footprint

100–€180/mo

What you see is a fraction of what goes in

Every module represents a curated slice of work. The estimate shows engineering time. It does not show the architecture decisions, the hardening, or the edge cases compressed into each one.

What you see in the estimate
Module listHour rangeMonthly cost
What is underneath

System-level indicators

These aggregate signals reflect the overall impact of the selected configuration across all applications and modules. Each one rolls up lower-level metrics to give a sense of where complexity, effort, and cost are concentrated.

Module-level indicators

Per-module signals that appear as coloured dots on each capability module. They show the relative scope, engineering depth, and platform footprint of that individual module.

Raw engineering metrics

The underlying data points that feed into the indicators above. These are never shown directly in the estimator but are used internally to calculate each indicator score.

How we work

Six engineering principles that compound over time. The more projects we complete, the more efficient the next one becomes.

Reusable by default

Write once, deploy everywhere

Every component, hook, and utility is a reusable module from day one. Bug fixes propagate everywhere, new features build on proven foundations that have been validated in production.

Modular architecture

Swap, scale, or extend any part

Systems are composable modules with clear boundaries. Each module owns its data, logic, and UI. Add, remove, or upgrade any part without touching the rest. Maintenance stays linear as the system grows.

Stability over novelty

Proven tools, predictable results

Boring, well-understood technology over the latest trend. Every dependency is evaluated for long-term maintenance cost and community health. Your platform runs on tested foundations.

Performance as a feature

Fast by architecture, not afterthought

Static generation, edge caching, code splitting, lazy loading, and optimised queries are part of the default setup. Sub-second page loads and green Core Web Vitals out of the box.

Automated quality gates

Catch problems before production

Every commit runs through automated tests, type checking, linting, and build verification. Regressions are caught in minutes, not discovered by users. We deploy confidently and frequently.

Pragmatic to the core

Maximum output, minimum complexity

If something can be generated, we generate it. If a pattern repeats, we abstract it. If a step can be automated, we automate it. Less code means fewer bugs and lower costs; savings passed to you.

Build your estimate in the Project planner

Select modules to generate a personalised review