Straight answers before the fit call.

No. Custom software is one deliverable. The engagement starts with how your company operates: we map that work, then encode it in software you own.

A conventional software shop may stop when the code ships. The PNS Method keeps business intent readable, EHOS governs execution and evidence, and Shugyo helps leaders see what to improve after handover.

Low-code platforms help non-engineers assemble applications. The PNS Method lets business owners shape intent, while a technical owner governs implementation through EHOS.

Those rules are part of the working environment, rather than an optional layer added later.

SaaS partners help you configure software that someone else built. We help you build software shaped to your business.

A SaaS implementation can be successful and still leave a poor fit between the product and your process. That is usually when this approach becomes relevant.

An internal engineering team still has to establish the process map and runtime, connect the intelligence layer, and maintain the whole system. We bring a working approach for doing that, then transfer it to your team.

The intended result is an operating system your internal team can run without depending on us indefinitely.

No. You own the codebase, data, and configuration. Your agreement also gives you the right to use the runtime. If we stop being the right partner, your team can keep operating the software.

The first useful surface ships within the first month of the encode stage. The map takes days to weeks before that, depending on the size of the operation.

Progress is demonstrated in working software inside the runtime, rather than documents alone.

Each service page publishes a starting-from price and a typical duration. Domain-Driven Process Modeling starts from EUR 8k (1 week, a five-day workshop). AI-Ready Data Foundation starts from EUR 15k (4-8 weeks). AI Engineering Practice starts from EUR 10k (4-6 weeks plus optional retainer).

At the fit call, we price the scope based on the size of the process, its regulatory requirements, and the requested delivery pace. Each engagement has a fixed price. There is no paid discovery phase or time-and-materials billing.

For a longer runtime build, the completed map leads to a fixed proposal. After launch, an optional retainer is based on how often the business and its software need to change.

The fit call is free.

The runtime enforces access controls and audit records beneath each application. It also handles data lineage and retention, secrets, identity, and separation of duties.

Controls required for SOC 2 and equivalent standards are configured in the runtime from the start.

( Shugyo is a separate product with its own surface at shugyo.ai ; canonical answers about Shugyo live there.)

You choose whether Shugyo runs in your cloud or ours. We document that choice before the engagement starts, and you own your data from day one.

We do not train shared models on customer data. Your instance of Shugyo is yours alone.

Yes. We use AI during every stage of the engagement. It helps with repetitive work, prepares drafts for review, finds patterns in operational data, and estimates the cost of delays.

It is part of our delivery process as well as the resulting software where the use case calls for it.

No. We take responsibility for an operating-system engagement rather than supplying individual team members.

Yes. The explicit entry engagement is Domain-Driven Process Modeling: a five-day workshop with a fixed price from EUR 8k. You leave with a domain map for one named process.

That map becomes the business-readable contract for the build. Starting with one process keeps the first service specific and tied to work the company cares about.

Regulated operations are a good fit for the runtime. It provides governance and auditability at the system level, including data lineage and separation of duties.

Our team has previous experience building software for regulated operations.

You do. Engagement contracts assign all IP produced in the engagement to the client.

EHOS is licensed for use; the operating model, code, data, and software governed through it are yours.

EmpoweredHouse turns business intent into software a company can own, govern, and improve. The PNS Method shapes the contract, EHOS governs execution and evidence, and Shugyo helps leaders see the company in motion. Shugyo has its own domain because customers can buy it separately as SaaS.

The named services cover the work needed to map a process, prepare its data, and build the software.

No. You can read the full method in your browser on the method page, without a download or email form. You pay for the runtime and the work required to apply the method to your company.

EmpoweredHouse is for founders and COOs deciding which business intent belongs in software they will own.

Shugyo is paid SaaS for operations and data leaders making a product decision. Its separate site gives that buyer a clear product story. Shugyo remains the intelligence leg of EmpoweredHouse.