ZORN NOVUM Start a Project
Menu
Workflow automation & integrations

Connect a defined workflow across your business tools.

Repeated copying, disconnected tools or a missing handoff can interrupt a business process. We assess focused automation and integration projects around a specific trigger, action and outcome, with the systems and permissions agreed in advance.

Your business need

Identify the handoff before choosing the integration.

Describe where the information starts, where it needs to go and what should happen next. The assessment depends on what the connected services actually allow, including their APIs, authentication, account plans and usage limits. A connection is scoped to the actions you authorize.

Possible projects

Examples to help define your scope.

These are illustrative project examples, not completed customer projects. Each request is assessed for fit before we agree to the work.

One workflow step

Pass the agreed fields from an approved request source to a supported business tool, with the trigger and result defined.

API, MCP and OAuth connections

Connect supported software APIs, or create an MCP server that exposes an agreed set of tools to a compatible client. Assess OAuth authorization where the services support it.

AI-assisted integration

Use an agreed third-party AI service within a defined workflow, with the input, output, review step and usage costs specified.

What the proposal defines

Know what will be delivered.

  • An agreed connection map: source, destination, trigger, permitted actions and field mapping.
  • The implementation and configuration instructions listed in the proposal, including the agreed authorization method.
  • Defined review cases for successful operations, errors and any required human approval, plus handover and support arrangements.

Deliverables, included revisions, acceptance criteria, third-party costs and recurring charges are specified in your proposal. Usage rights, ownership, licensing and any reuse or exclusivity arrangements are explained in the agreement.

Scope boundaries

An API or MCP connection is assessed individually; compatibility with every application or AI client is not assumed. Third-party changes, rate limits, paid plans and permission requirements can affect feasibility and cost. AI-assisted projects use agreed third-party services. Zorn Novum's original AI models remain in development and do not power these customer projects. Do not send credentials, tokens or private records in an initial inquiry.

Introductory pricing · USD

A starting point, followed by an individual quote.

Workflow automation starts at $350 for one defined workflow step. API and software integrations start at $750. AI-assisted tools and integrations start at $1,000.

MCP and OAuth work is assessed and quoted for the particular connection; no fixed MCP or OAuth package price is offered here. Managed AI integrations and automations are $149–$750+/month where agreed. Third-party AI usage and paid APIs are separately quoted or explicitly capped.

Starting prices apply to a defined scope, not every project in the category. Entry pricing assumes one defined function or adaptation of a permitted existing foundation. The initial consultation and project quote are free.

All service starting prices →
How we work together

Agree the work before it begins.

  1. Map the handoff

    Name the tools, describe the workflow and explain the permissions the connection would need.

  2. Assess the connection

    We review the supported interfaces and agree actions, data flow, review criteria, price and third-party costs before starting.

  3. Review the agreed behavior

    Check the specified success and failure cases, then follow the agreed deployment, handover and support arrangements.

Before paid work begins, we agree scope, price, deliverables, review, payment and support arrangements. Larger ideas may need a separately scoped first stage.

Read the project payment arrangements →

The agreement explains cancellation, refund, delivery and usage terms before payment. Integrations and more complex applications are assessed individually before any commitment.

Before you inquire

Common questions

What is an MCP connection for?

Model Context Protocol (MCP) lets a compatible AI client use tools exposed by a server. A project defines which tools are exposed and which systems they can access; it does not imply unrestricted access or compatibility with every client.

Can you connect any two applications?

Each connection needs assessment. The applications must provide suitable supported interfaces and permissions for the requested workflow. Some ideas may need a separately scoped first stage or may not be a fit.

Are AI usage and API subscription fees included?

Only as expressly stated in the proposal. Third-party usage, paid APIs and limits are separately quoted or explicitly capped. Recurring management and variable usage charges follow the agreement.

Should I send API keys with my request?

No. Start with application names and a general description of the workflow. Any credentials or authorization needed for an accepted project must follow the handling arrangements agreed for that work.

Tell us what you want to improve.

Describe the need, how you handle it today and who would use the result. Please do not include passwords, credentials, sensitive files or private customer records.

Request a Free Project Quote →

Prefer email? Write to orders@zornnovum.com. A request does not place an order or commit either party to paid work.

Explore all business services →

Selected software services operate separately from our proprietary business AI platform, which is still in early development. Read about the AI direction.