Airise / Proposal / 001
20 MAY 2026
CONFIDENTIAL — PROPOSAL

Proposal for
[Subject 001].

This engagement covers the automation of core operations and the build-out of internal systems for a regional services company. The objective is to reduce manual overhead, sharpen information flow, and leave the client with tools they own and understand.

§ 00 VALIDITY
30 DAYS
00 HOURS
00 MINUTES
00 SECONDS
§ 01 SITUATION

Operations-led businesses accumulate process debt the way software accumulates technical debt. The difference is that process debt is invisible until it isn't — it hides in email threads, in spreadsheets passed by attachment, in the hours spent extracting information from one system to feed another. The cost is not dramatic. It is slow and continuous.

The engagement begins from the assumption that most of what needs to be done is already being done — just by people who should be doing something else. Automation here is not transformation. It is removal of friction. The goal is to reach the end of the engagement with fewer moving parts, not more.

§ 02 SCOPE
DELIVERABLES
    ENGAGEMENT MODEL
    —
    INVESTMENT
    —
    § 03 PHASES
    1. 01Initial briefing call with the operations lead and relevant stakeholders.
    2. 02Document current workflows, tools, and integration points across core functions.
    3. 03Identify and rank the top three bottlenecks by operational impact.
    4. 04Map data flows and dependencies between existing systems.
    5. 05Define success criteria and agree on measurement approach with the client.
    GATE Signed-off situation brief and confirmed scope. Nothing moves to Design without this document.
    1. 01Propose automation architecture for each identified workflow, sequenced by impact.
    2. 02Review with client; refine based on operational constraints and team capacity.
    3. 03Define data models and integration contracts between systems.
    4. 04Agree on tooling stack — avoiding vendor lock-in by default.
    5. 05Finalize delivery scope and write formal acceptance criteria.
    GATE Approved design document. Design gate triggers the 40% milestone payment.
    1. 01Configure and build automation systems per the agreed design.
    2. 02Integrate with the existing software stack at each defined touchpoint.
    3. 03Internal testing against the agreed acceptance criteria.
    4. 04Client UAT session — one round of revisions is included in scope.
    5. 05Performance hardening and edge-case handling.
    6. 06Draft documentation completed in parallel with the final build.
    GATE Client sign-off on UAT. All acceptance criteria met and documented.
    1. 01Final documentation package delivered to the client.
    2. 02Live walkthrough session with the client's operational team.
    3. 03Two-week monitored live period — Airise on call for critical issues.
    4. 0430-day async support window opens post-handover.
    5. 05Retrospective brief with recommendations for the next phase of work.
    GATE Handover accepted in writing. Final 20% payment released. Engagement closed.
    § 04 BOUNDARIES
    INCLUDED
    • +Workflow audit, design, and automation build
    • +Integration with existing tools and platforms
    • +One round of revisions per workflow
    • +Full documentation and operating guides
    • +Staff handover and walkthrough session
    • +Post-launch support window (duration by tier)
    • +Final retrospective and recommendations brief
    NOT INCLUDED
    • —New software subscriptions or SaaS licensing fees
    • —Hardware procurement or infrastructure setup
    • —Ongoing maintenance beyond the support window
    • —Content creation, copywriting, or design assets
    • —Anything not specified in the agreed scope document
    § 05 INVESTMENT
    SELECTED TIER  /  ESSENTIAL
    —
    PAYMENT STRUCTURE
    ON SIGNATURE 40%
    DESIGN GATE 40%
    HANDOVER 20%
    § 06 ACCEPTANCE

    This document is a proposal, not a contract. Acceptance here signals intent to proceed and authorises Airise to issue a formal service agreement.

    Airise operates selectively. Acceptance opens a brief due-diligence period before the service agreement is issued. We reserve the right to decline engagements that are not the right fit.

    This is a proposal. Not a promise.

    This document is non-binding until a service agreement is countersigned by both parties. It is valid for 30 days from the date of issue. Terms, investment figures, and timeline estimates are subject to confirmation following the discovery phase.