Skip to content
Pyrana

Solutions

Any process with rules. Nine examples.

The platform is not tied to a function or an industry. Any process with data, rules, and approvals can run as an App. The nine below are examples chosen for range across finance, operations, customers, people, and control functions; each is configuration on the same platform: pages where people work, targets reached through one gate, workflows that fan out to specialized agents, approval lanes named in policy, and one execution record. Every App after the first reuses the identity model, the access profiles, the approval lanes, and the record, because those live in the platform rather than in the App. That is where speed to value comes from.

Business function owners

Nine examples

Each written as the work today, what the App does, and who approves what. Any other process follows the same shape.

AI, data, and IT owners

The platform

What is decided where, and why the foundational engineering is never redone.

Builders

The mechanisms

The gate, lanes, approval policy, extensions, provenance.

01Financial close and review

A month-end close with the evidence attached.

Doorsschedulecopilotpages
Approvalscontroller lane above 25,000 USD
Contextclose policychart of accountsprior-period commentary
Demo: financial analysis
The work today
Month-end runs on spreadsheets, email threads, and a controller who reads every entry because nobody else can. Variances surface late and commentary is written at midnight.
What the App does
A close App runs on a schedule: the workflow fans out to specialized agents per entity, each reconciling intercompany balances, drafting accruals from open POs, and posting what falls inside its entitlement. Findings publish back to the App as versioned resources. The controller reads a short list of exceptions on the review page, with the evidence attached, and approves there or through the copilot. The auditor reads one execution record.
Who approves what
Journal entries above the threshold freeze for the controller lane. Intercompany mismatches route to the owning unit's controller. Everything below threshold posts with a receipt.
Pyrana Capital Finance / Monthly analysis / PMW · June 2026

PMW · June 2026

Monthly pack · published v2 by the copilot on behalf of J. Okafor

Published v2Add to chat

Revenue

$12.4M

-$2.5M year over year

Materials

-$188K

PPV breach, Mar and Apr

Labor

31.2%

of revenue · plan 30.0%

Findings

4

1 needs approval

Illustrative. Synthetic data.

02Collections

The aging report worked every morning, with one packet per dispute.

DoorsschedulepagesAPI from the AR system
Approvalscollections lead for write-offs and plans
Contextcredit policycontract termscustomer history
The work today
The 60-day bucket grows while the team works the accounts it can remember. Promises to pay live in inboxes. Escalations happen when someone notices.
What the App does
A collections App runs from a schedule each morning: the workflow matches remittances, drafts outreach from the customer's history and tone, schedules follow-ups, and assembles each dispute into one packet with the invoice, the contract clause, and the payment history. The team works the queue on the App's pages. Escalations route to the collections lead with the packet attached.
Who approves what
Write-offs and payment plans above policy freeze for the collections lead. Customer-facing messages above a sensitivity threshold require a reviewer.
Action Items

Action Items

Identified by the Apps' runs, owned by people.

Board

Open

12

identified this week

In progress

3

Resolved

9

75% completion

Open

revenueHIGH

Rebuild APL account revenue to narrow the shortfall

Accept

In progress

collectionsMED

Work the 60-day bucket for Greenfield Agriculture

Resolved

closeDONE

Post intercompany adjustment PMW/MWM

Illustrative. Synthetic data.

03Procurement

Purchase requests with the policy applied as they are written.

DoorspagescopilotAPI from the ERP
Approvalsprocurement lead above 50,000 EURvendor onboarding for new vendors
Contextprocurement policyvendor recordscontract terms
The work today
Buyers copy policy from a PDF into a request, approvers ask for context that was never attached, and preferred vendors are discovered after the PO is raised.
What the App does
A procurement App works on the buyer's page: as the request is written, an agent fills in the contracted vendor and price, checks the budget line and the DPA on file, attaches the quotes, and flags a request that exceeds the buyer's authority before it is submitted. The director approves in the lane the policy names. Requests raised in the ERP arrive through the API and pass the same gate.
Who approves what
Spend above a threshold freezes for the procurement lead. New vendors require the vendor-onboarding lane. Cross-border purchases require a signed DPA on file.
Review / Approval queue

Review

Approve, return, or edit what the policy routed to you.

Role: Reviewer

Journal entry · PMW intercompany adjustment

38,400 USD · proposed by the reconciliation workflow

6 of 6 policy checks passlane pmw-approvers

ApproveReturn

Vendor onboarding · Nordholm Logistics

New vendor · DPA on file · proposed by the procurement App

5 of 6 checks pass · tax form missinglane vendor-onboarding

Returned with a note

Illustrative. Synthetic data.

04Marketing content

Content that carries its own review record.

Doorspagescopilot
Approvalsreviewer lane on publishcompliance lane for regulated claims
Contextbrand guidelinesapproved claims libraryprior baselines
Demo: document redaction
The work today
Drafts move between tools, reviewers comment on stale versions, and the approved baseline is whichever file was emailed last.
What the App does
A content App holds drafts, review entries, and published baselines as versioned resources. Writers draft on the App's pages with an agent, submit a review entry that persists, and a separately authorized reviewer approves. Publishing against a stale version is refused, never overwritten. Every earlier baseline stays browsable and citable.
Who approves what
Maker-checker on every publish. Claims that touch regulated language route to the compliance lane.
Review / Approval queue

Review

Approve, return, or edit what the policy routed to you.

Role: Reviewer

Journal entry · PMW intercompany adjustment

38,400 USD · proposed by the reconciliation workflow

6 of 6 policy checks passlane pmw-approvers

ApproveReturn

Vendor onboarding · Nordholm Logistics

New vendor · DPA on file · proposed by the procurement App

5 of 6 checks pass · tax form missinglane vendor-onboarding

Returned with a note

Illustrative. Synthetic data.

05IT project management

Project status as a record, not a report.

DoorspagescopilotAPIMCPschedule
Approvalsrelease manager for production
Contextrelease policyproject graphQA gate results
One operation, five doors
The work today
Status is assembled by hand from three trackers. Stale projects sit in review for weeks. Nobody can say who moved what, or why.
What the App does
An IT-PM App owns the project graph in a client extension with its own durable storage. A manager moves a card on a page, a colleague asks the copilot to move it, and a nightly workflow advances stale projects. All three resolve to the same target, pass the same gate, and write to the same transaction. Syncs to external trackers run as governed effects.
Who approves what
Transitions to production require the release-manager lane. The nightly workflow waits for a person when the policy says so.
Project Portfolio

Project Portfolio

What is in flight, and how healthy it is.

25 tracked projects

Total projects

25

Value captured

$4.5M

28% of planned

Budget

$5.5M

of $10M planned · $4.7M under

Backlog1

PRJ-0015

Retail media measurement

PM J. Amara

+ Add to chat

Charter1

PRJ-0012

Supplier risk scoring

PM N. Bakhtiari

+ Add to chat

Execution2

PRJ-0006

ERP integration hardening

PM M. Oyelaran

Move to Production · awaiting release manager

Value realization1

PRJ-0018

Contract lifecycle rollout

PM C. Vandermeer

$240K captured

Illustrative. Synthetic data.

06Compliance and risk

Controls with provenance.

DoorsschedulepagesAPI
Approvalscontrol owner for exceptionscompliance for policy changes
Contextpolicy librarycontrol matrixregulatory updates
Demo: compliance document analysis
The work today
Policies live in documents, controls live in spreadsheets, and evidence is gathered in the two weeks before the audit.
What the App does
A compliance App runs on a schedule: the workflow fans out to agents that scan policies and controls, track regulatory change, and publish findings with full provenance: which control, which policy unit, which source line. Evidence accumulates as records in the App, read on its pages and through the API, rather than assembled before the audit.
Who approves what
Control exceptions require the control owner's lane. Policy changes that affect regulated units require compliance sign-off before they take effect.
Compliance Center / Applications I manage

Applications I manage

Run an automated control audit against a connected application.

Identity admin console

MFA · admin.example.okta.com

5 of 6 pass
Run compliance checkHistory →

Last run · Identity admin console

Evidence captured by a governed browser session · Sep 10, 2026

  • MFA enforced for all admins
  • Session timeout at or under 30 minutes
  • No shared admin accounts
  • Audit log retention 12 months or morefinding

Illustrative. Synthetic data.

07Customer service and case resolution

Resolve the case with the policy and the history in view.

DoorspagesAPI from the CRMcopilotschedule
Approvalsservice lead above thresholdproduct team for policy exceptions
Contextservice policyentitlementscase history
The work today
Cases bounce between queues. Agents on the phone search three systems for the order, the contract, and the last promise made. Escalations depend on who is on shift.
What the App does
A service App holds the case: the workflow assembles the customer's orders, entitlements, prior cases, and the applicable policy units, drafts the resolution, and issues credits inside its authority. The person on the case sees one page with the evidence attached and decides. Refunds and exceptions above policy queue for the lane the policy names.
Who approves what
Credits above threshold freeze for the service lead. Policy exceptions route to the owning product team. Customer-facing messages on regulated products require a reviewer.
Action Items

Action Items

Identified by the Apps' runs, owned by people.

Board

Open

12

identified this week

In progress

3

Resolved

9

75% completion

Open

revenueHIGH

Rebuild APL account revenue to narrow the shortfall

Accept

In progress

collectionsMED

Work the 60-day bucket for Greenfield Agriculture

Resolved

closeDONE

Post intercompany adjustment PMW/MWM

Illustrative. Synthetic data.

08Supply chain and inventory

See the shortage before the line does.

DoorsschedulepagesAPI from the ERPMCP
Approvalssupply lead for expeditessourcing lane for supplier changes
Contextlead-time policysupplier termsdemand history
The work today
Planners reconcile forecasts, purchase orders, and supplier confirmations in spreadsheets. A late shipment is discovered when a work order cannot start.
What the App does
A supply App runs from a schedule: the workflow fans out per plant and per supplier, compares demand against confirmed supply, flags shortages and excess with the lead-time policy applied, and proposes expedites, substitutions, and reorder changes. The planner reviews the proposals on one page; changes to purchase orders post only inside the planner's authority or through the approval lane.
Who approves what
Expedites above cost threshold freeze for the supply lead. Supplier changes require the sourcing lane. Safety-stock policy changes require compliance sign-off where regulated.
Dewsy Performance Intelligence / Overview
OverviewAmazonDTCPaid mediaSearchAction planData through Jun 30, 2026

Sales vs plan

19%

trailing

Blended return

0.77x

breakeven near 2.2x

Marketing efficiency

0.93

sales per ad dollar

Monthly net

-$334k

cash out vs in

AmazonConfirmed

The scented serum's low Amazon conversion is a traffic problem, not the listing

Paid TikTok traffic points at the serum's Amazon page, where the ad pixel attributes zero purchases. Sponsored clicks convert at about 10.2%, so the fix is the traffic. cxu 4e9a…

View the full diagnosis →

Illustrative. Synthetic data.

09HR and people operations

Onboarding that follows the policy, not the checklist someone remembers.

DoorspagesAPI from the HRISschedulecopilot
Approvalsidentity lane for access beyond profileHR and manager for compensation
Contextrole profilesonboarding policyregional requirements
The work today
A new hire's first week depends on tickets across HR, IT, facilities, and finance. Access is over-provisioned because nobody knows the exact profile for the role.
What the App does
A people App runs each hire as a governed process: the workflow provisions accounts to the access profile the role defines, schedules training that the policy requires, opens the equipment and badge requests, and reports what is done and what is waiting. Managers and HR see one page. Anything that grants access beyond the role's profile, or touches compensation, waits for the lane the policy names.
Who approves what
Access beyond the role profile freezes for the identity lane. Compensation and contract changes require HR and the hiring manager. Terminations run the same process in reverse with the same record.
Review / Approval queue

Review

Approve, return, or edit what the policy routed to you.

Role: Reviewer

Journal entry · PMW intercompany adjustment

38,400 USD · proposed by the reconciliation workflow

6 of 6 policy checks passlane pmw-approvers

ApproveReturn

Vendor onboarding · Nordholm Logistics

New vendor · DPA on file · proposed by the procurement App

5 of 6 checks pass · tax form missinglane vendor-onboarding

Returned with a note

Illustrative. Synthetic data.

07Beyond the examples

Any repeatable process with rules, data, and approvals.

The examples above are a sample, not a catalog. The App document, the gate, the approval lanes, and the context engine are the same for a process the platform has never seen. Twelve functional areas where the same shape applies.

  • Finance and accounting

    Close, consolidation, accruals, intercompany, FP&A commentary, AP and AR, treasury, expense review.

  • Sales and revenue operations

    Pipeline hygiene, quoting and pricing approvals, renewal forecasting, churn signals, territory and commission reconciliation.

  • Marketing and eCommerce

    Channel-aware content, campaign performance diagnosis, catalog enrichment, promotion analysis, brand-rule review.

  • Customer service and success

    Case assembly and resolution, entitlement checks, credits inside authority, escalation with the evidence attached.

  • Procurement and sourcing

    Requisitions with policy applied, vendor onboarding, contract compliance, spend against budget lines.

  • Supply chain and logistics

    Demand against confirmed supply, shortage and excess detection, expedites and substitutions, supplier performance.

  • Manufacturing and quality

    Deviation and CAPA workflows, batch record review, SOP-bound checks where the policy unit and its source line matter.

  • Human resources and people operations

    Onboarding and offboarding to role profiles, policy-bound access, compensation changes with approval lanes.

  • Legal and contracts

    Clause review against playbooks, obligation tracking, matter intake, maker-checker on outbound documents.

  • Risk, compliance, and internal audit

    Control testing with captured evidence, policy change tracking, regulatory monitoring, audit-ready records.

  • IT operations and service management

    Project portfolio governance, incident triage, change approvals, SaaS control audits, configuration drift.

  • Data, analytics, and research

    Data quality monitoring, cross-source reconciliation, market and scientific research with cited findings, report generation.

08Examples by industry

Industry-agnostic. Strongest where the rules matter most.

The rules, the data, and the approvals change by industry; the platform does not. Public, private, and PE-backed businesses, in regulated environments that need audit trails, data residency, and governance controls. Twelve industries where the platform applies.

  • Financial services and banking

    Close, reconciliation, KYC and onboarding, credit review, with records auditors and regulators can read.

  • Insurance

    Claims triage and adjudication support, underwriting workups, policy servicing under filed rules.

  • Private equity and portfolio companies

    Multi-entity close, portfolio reporting, value-creation tracking, one governance model across holdings.

  • Life sciences and pharma

    SOP-bound and validated processes, regulatory submissions support, epidemiology and evidence pipelines with provenance.

  • Healthcare providers and payers

    Prior authorization, revenue cycle, care coordination workflows under privacy and consent rules.

  • Manufacturing and industrials

    Quality and deviation management, supply planning, maintenance and asset workflows across plants.

  • Energy and utilities

    Asset and field work orders, regulatory reporting, outage and compliance evidence.

  • Retail, consumer, and eCommerce

    Channel performance, pricing and promotion decisions, catalog and content operations, launch diagnostics.

  • Hospitality and travel

    Multi-property close and procurement, revenue management, guest-service cases with approval authority that follows the org chart.

  • Technology and software

    Release governance, SaaS compliance checks, customer-success operations, usage and renewal signals.

  • Legal and professional services

    Matter and engagement workflows, playbook review, deliverables where maker-checker and provenance are the product.

  • Public sector and education

    Case management, grants and procurement under statute, records that must survive an audit or a records request.

09How an engagement runs

Six weeks to the first App. Less to the second.

The timeline is typical for a first App and is confirmed per engagement. With clean data available, the App document itself typically stands up in about a week; the frontend experience, the access profiles, and the knowledge loaded into cortIQ take the rest.

  1. Week 1Define

    The process is named: the owner, the cycle time today, the systems it touches, and the approvals. SSO is connected.

  2. Weeks 2 to 3Bind and extend

    Access profiles and approval policy are written. The documents that matter are loaded into cortIQ. Systems are connected through tool sources; an extension is added where domain code needs one.

  3. Weeks 4 to 5Pilot in production

    The App runs on real identities with real approvals and a real record. Cycle time and exceptions are measured against the baseline.

  4. Week 6Activate

    The active pointer moves to the compiled version. The identity model, profiles, lanes, and record are assets the second App starts with.

Agentic applications, not agents.

Built once. Configured per application.

Book a demoDemos