Software for the work behind your business

Different work.
One connected direction.

From requests and quotations to approvals and handoff.
PHASAN is building tools for these everyday operations
and a foundation to connect them.

PHASAN Work is in internal testing

RequestQuotationApprovalHandoff
PHASAN
Conceptual connections, not a product screenshot

One job.
One trail.

Requests, agreements and decisions should stay with the work until handoff.

Illustrative data. The Kote–RequestOS connection is still in internal testing.

One job · one trailREQ-0117 → EV-0042
  1. Request · RequestOSREQ-0117

    Brochure redesign, Thai and English

    Captured from a client chat

  2. Quotation · KoteQT-0042

    ฿48,500 · two revision rounds

    Second version sent

  3. Approval · RequestOSAP-0042

    Discount above policy needs sign-off

    Approved by the operations lead

  4. Project · KoteJOB-0042

    Kickoff Monday · brand assets requested

    In progress

  5. Evidence · KoteEV-0042

    Signed scope and delivery files

    Waiting for handoff

Illustrative, not customer data

Everyday work

One job.
Context everywhere.

Every handoff means finding the context all over again.

Scattered tools

Chat · documents · decisions

What we are building

Keep context with the work for the next person.

The workflow

From request to handoff

Each step keeps the details needed to review and carry work forward.

Stage 1 / 6

Request

Capture the ask and its details before work begins.

Stage 2 / 6

Review

Agree on the scope and quotation so everyone starts with the same context.

Stage 3 / 6

Approval

Record the decision, its owner and the reason behind it.

Stage 4 / 6

Execution

Track the next step and hand it to the person responsible.

Stage 5 / 6

Evidence

Keep documents and evidence alongside the work they support.

Stage 6 / 6

Handoff

Confirm acceptance and pass on the details needed to continue.

Illustrative workflow. Cross-product connections remain in internal testing.

Our starting point

PHASAN Work

Give client work a clear next step.
From the first ask to handoff.

Internal testing

Kote is available independently. RequestOS and the joined experience are not yet open to customers.

Explore Kote

Kote

Quotations and client work

Available independently

RequestOS

Requests and approvals

Internal testing
Target connection through PHASAN Core

PHASAN solutions

Different kinds of work.
Tools to suit each one.

Purpose-built combinations at different stages of development.

Internal testing

PHASAN Work

Requests, quotations and approvals

Designing connections

PHASAN Services

Appointments, service jobs and handoff

Planned

PHASAN Commerce

Orders, store operations and evidence

Planned

PHASAN Creator

Scope, revisions and bookings

Planned

PHASAN Learn

Assignments, deadlines and resources

Planned

PHASAN Property

Facilities, assets and acceptance

Planned

PHASAN Operations

Requests, reviews and field evidence

Planned

PHASAN Life

Personal and family routines

Explore the products in each solution

PHASAN Work

Kote · RequestOS

PHASAN Services

Kote · Appoint · RentalOS

PHASAN Commerce

Kote · Mori · JaneQ

PHASAN Creator

Kote · Appoint · JaneQ

PHASAN Learn

Appoint · DekTask · JongSpace

PHASAN Property

Kote · RentalOS · JongSpace

PHASAN Operations

Kote · RequestOS · JaneQ

PHASAN Life

LifeOS

Planned product coverage. No solution is yet available as a complete integrated bundle.

A shared foundation. Clear boundaries.

Each product
owns its work.

Connected through PHASAN
with its own data and permissions.

Read the platform approach

PHASAN Core owns identity, the product registry and coarse access entitlements. Products own their business data, databases and domain rules. Shared accounts and complete cross-product journeys are not yet live.

SolutionsProducts combined around a workflow
Independent productsProduct-owned data and domain rules
PHASAN CoreIdentity · registry · entitlements
Target architecture, under development

What we believe

Work that repeats
should not start from scratch
every time.

Build each part well. Then join the parts
when real use proves the connection matters.