Private workflow software, governed by requirements your organisation can review.

A private tool is a scoped build against a written quote, and for most teams it is the right answer. An enterprise engagement adds the review and documentation layer around it: qualification, a data and integration review, a feasibility assessment, procurement-ready scope, agreed acceptance criteria, and contract-defined responsibilities. If your organisation does not need that layer, the private-tool route is faster and cheaper.

Reuse of existing capability is assessed during review, and where a maintained product already fits, you will be told to use it. What does not happen is a shared product being modified for one organisation — the products are maintained for everyone who uses them. A requirement that needs different behaviour becomes its own scoped build instead.

It has to be reviewed rather than assumed. There is no public Motifuse API and no standing catalogue of integrations, so each connection is assessed for technical feasibility, the access and credentials required, permissions and rate limits, failure handling, ownership, and any provider cost. If the review says it is workable, it goes into the proposal with its responsibilities written down; if not, you are told that before money is spent.

Often, where the operation and the file sizes allow it — most of the public tool directory works this way, and no request carrying your content is made. Whether it holds for your workflow is confirmed during technical review, because volume, file size and the operations involved all decide it.

It is sent for the specific action requested. Requests are validated against a schema with a size limit before a handler sees them, travel over HTTPS, and are authorised against the owning account — a record you do not own answers as not found. What is retained afterwards, and for how long, is set in your scope rather than by a default.

Not today. Sign-in is by password or an emailed sign-in link, sessions are held in a first-party cookie for about 30 days, and access is scoped to the individual account. There is no directory sync and no role-based permission system. Any access model beyond named accounts would have to be specified, built and verified before it could appear in a proposal — it is not something to plan around today.

It is a reviewed option, not a standard entitlement. Motifuse-managed delivery is the standing capability. A customer-controlled environment requires a technical and security review covering deployment, maintenance, updates, monitoring, ownership and support responsibilities, and it only becomes real once it is written into the agreement.

The public security overview describes the controls that are actually implemented — HTTPS with HSTS and a content security policy, schema and size validation before any handler runs, cookie sessions with a trusted-origin check against cross-site request forgery, and owner filters bound into database queries. For an engagement, the data-flow description, processing model and responsibilities are produced as scope documents. Motifuse holds no compliance certification and does not represent otherwise.

Per engagement, after review. The estimate reflects workflow complexity, user roles, data volume and formats, integrations, the processing model, hosting requirements, validation depth, documentation, timeline and support expectations. A proposal states a setup fee and any recurring fee. No prices are published, because two requirements that sound similar routinely differ several-fold in work.

Scope and exclusions, deliverables, responsibilities on both sides, the processing model, the integration inventory where relevant, acceptance criteria, test scenarios, milestones, commercials, and the support arrangement. It is written to be read by procurement and by the people who will use the result.

Clarifications during a build are expected. A change that alters the approved scope is raised as a change request, reviewed, and then either included without charge or estimated separately before it is implemented — so scope and price never drift apart quietly. Larger changes can become their own phase.

What the agreement says, and nothing implied beyond it. Support hours, response arrangements, escalation, maintenance and continuity are commitments only where they are written into the contract. There are no published uptime or response-time guarantees, and no dedicated account management.

Ownership, source-code access, hosting rights, licensing and reuse are defined in the agreement for that engagement. There is no standing arrangement that transfers source code by default, so if ownership matters to your organisation, raise it during review rather than at handover.

Motifuse holds no compliance certification and will not claim conformance with a framework it has not been audited against. What it can do is document the data flow, processing model, access model and responsibilities so your own compliance team can assess them. Where a requirement genuinely depends on a certification, the review will say so plainly rather than work around it.