The questions that come up before the fit call.

No. Custom software is the deliverable. The work is encoding the operating system of a company in software the company owns.

The difference is the process map, the runtime, and the intelligence layer. Custom software shops ship code. We ship a company that runs on its own software.

Low-code platforms let non-engineers build toys. Process Native Software lets operators contribute to the operating system of the company, inside a runtime that enforces governance, security, and audit.

Low-code skips the rules. We make the rules the room.

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

The two are not in competition; the SaaS partner has done their job, and the fit is still wrong, which is why you are reading this.

An internal engineering team needs a runtime, a process map, an intelligence layer, and the discipline to keep all three working. We bring those, and then we hand them over.

The right end state is that your internal team operates the operating system we built together. We do not want to be in your codebase forever.

No. You own the runtime, the codebase, the data, and the configuration. The engagement is structured so that if we stop being the right partner, you keep operating.

Lock-in is what the average vendor sells. Ownership is what we sell.

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.

We do not ship paper milestones; we ship working software inside the runtime.

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).

What changes the number is sized at the fit call: the size of the process, the regulatory weight, the speed you want it run at. Each engagement is fixed-price; no discovery phase, no time-and-materials.

Beyond the entry engagements, the longer runtime build is sized to the leverage on offer; the map produces a fixed proposal for the build. The post-launch stage is a retainer, sized to the actual rate of change in your business.

The fit call is free.

Properties of the runtime, not features of the application. Access, audit, data lineage, retention, secret management, identity, separation of duties, all enforced at the substrate.

SOC 2 and equivalents are configuration, not a project we run later.

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

In your cloud or in ours, your choice, documented before the engagement starts. Data ownership is yours from day one.

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

Yes, throughout. AI sits in the loop during the map, the encode, and the evolve stages. It does the boring work, drafts the next move, watches the patterns, surfaces the cost of every delay.

AI is not a feature of the product; AI is part of how the work gets done.

No. Either we engage on the operating system or we do not engage.

Yes. The explicit entry engagement is Domain-Driven Process Modeling: one week, a five-day workshop, fixed price from EUR 8k, deliverable is the domain map of one process you can name.

From there, the map becomes the contract Process Native Software is generated from. We do not start with a feature; we start with a process the company can name and that the founder cares about.

Better. Regulated operations are where the runtime earns its keep most clearly. Governance, audit, lineage, and separation of duties are runtime properties, not features we add later.

We have built for regulated operations before.

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

The runtime itself, Process Native Software, is licensed to you for use; the operating system we encode on top of it is yours.

We are a platform company with a services arm. The platform has two surfaces: Process Native Software, the runtime, which lives inside EmpoweredHouse; and Shugyo , the intelligence layer, which lives on its own domain because the paid SaaS has its own commercial motion.

The services (three named engagements) are how a company gets onto the platform. The platform makes the services compounding; the services make the platform real.

No. The full method is a visual page you read in the browser at the method page. No download, no email gate, no funnel. The runtime that operationalizes the method is the part you pay for.

Different buyer, different funnel. EmpoweredHouse sells the runtime and the engagements that land you on it: the buyer is the founder or COO making a platform decision.

Shugyo is a paid SaaS with its own commercial motion: the buyer is operations or data leadership making a product decision. Keeping the surfaces apart protects both stories and lets each domain build its own SEO authority. Internally they are the same platform.