Skip to content
Harborby Signalry
Tech / digitalThis sitting

Job brief

Turn an intent into an underwriting packet

How and who for the hotel job—verified when attested.

When I have a claim and a price, I want a structured packet a future underwriter could refuse — so we stop talking in slogans.

Usable on this screen

Scoped brief

The form writes locally. The API stub echoes. Export JSON. That is v1. A licensed desk is a later company problem, not a checkbox on this page.

Outcome
JSON: claim, evidence, caveat, criteria, price, persona, stack. Status is demand-signal. licensed is false.
Catalog budget band
Zero premium — the packet is the product today. A worksheet range, not a quote.
Catalog timeline
Fifteen minutes on /verified-outcomes. Not a promise.
  1. Step 1

    Fill claim → evidence → caveat → price

    Missing evidence drops the packet to advice or claimed. Harbor will label it.

  2. Step 2

    Export the packet

    harbor-underwriting-packet.json. Keep it with the house. Do not put folio text in it.

  3. Step 3

    Sit a pilot if you want a longer read

    The 30-minute sit on /pilots is how a design partner corrects the how.

  4. Step 4

    Refuse the packet if it reads like a policy

    licensed:false on the same page as the price. A prettier button that implies cover fails the brand.

Provider shortlist

  1. Software· demo

    Caveat Ledger (demo desk)

    Named claim / evidence / caveat worksheet

    Catalog score 7.5. A post-job shape, not a verification. Stable id caveat-ledger.

  2. People

    Outcome Desk

    Verified-outcome packets for hotel jobs

    Catalog score 8.1. A post-job shape, not a verification. Stable id outcome-desk.

  3. Agent

    Evidence Scout

    Drafts an evidence line from a named job — never marks the house

    Catalog score 7.8. A post-job shape, not a verification. Stable id evidence-scout.

Leave a record

The next hotel starts from what you leave

Harbor by Signalry stays hotels only. A description, a claim, and a reported result each leave a stable id behind. Nothing here is a price, a customer, or a verification.

  • Buyer

    Describe your job

    No account. Harbor by Signalry opens the closest catalog brief, when not to buy, and a shortlist. A weak sentence stays on the catalog.

    Open a brief
  • Supplier

    Join as a supplier

    Company, jobs served, regions, and a hotel reference. The packet is queued as unverified pending. The form cannot mark it verified.

    Start a claim
  • Hotel

    Record a result

    A metric, before and after, and the dates. It is shown as reported until a person checks the evidence. Verified Outcome is not insurance.

    Record a result

AdviceAn underwriting packet that claims to be a policy fails integrity.

Situation

What is actually on fire

When I have a claim and a price, I want a structured packet a future underwriter could refuse — so we stop talking in slogans.

Approaches

Two or three paths — with the give

Honest stub

When. A file a future underwriter can refuse

You give. The sentence 'you're covered'

Fake policy UI

When. A prettier button

You give. The brand

Who to involve

  • · Hotel tech lead
  • · GM (sign-off)
  • · Night audit / reservations
  • · Payments or QSA partner

First 7 days

YAML-shaped: day / theme / tasks / owner / risk / exit. Advice until a case is verified.

  1. day: 1

    Write the fail in one sentence

    • · Write the fail in one sentence. Job: Turn an intent into an underwriting packet.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  2. day: 2

    Pull the last 7 days of the live number

    • · Pull the last 7 days of the live number. If it is missing, that absence is the finding.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  3. day: 3

    Name who owns the workaround today (desk,

    • · Name who owns the workaround today (desk, HK, night audit, owner).
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  4. day: 4

    Walk one peak hour

    • · Walk one peak hour. Write what the system claims vs what the floor did.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  5. day: 5

    Ask vendors the worksheet questions

    • · Ask vendors the worksheet questions. Discard anyone who cannot answer with a caveat.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  6. day: 6

    Pick one approach

    • · Pick one approach. Write when-not-to-buy on the same page.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open
  7. day: 7

    Run the smallest test that would change Mo

    • · Run the smallest test that would change Monday. No annual contract yet.
    owner:
    Hotel tech lead
    risk:
    The exit is not written down
    exit:
    A note the next shift can open

Decision worksheet

Questions, red flags, bands

Take this to a vendor call. Budget bands are Advice — a Harbor shape, not a quote.

Ask the vendor

  1. 1. Who types the status / number — a person, or your product?
  2. 2. What would have happened anyway in 90 days without you?
  3. 3. Show a property of this size and stack. Demo-labeled categories do not count as proof.
  4. 4. What can your agent never do (folio post, mark clean, change a rate)?
  5. 5. What is the kill-switch if guest comments move?

Red flags

  • · Calling licensed:false a quote.
  • · PII in the packet.
  • · Inventing a loss ratio.

When not to buy. Do not POST guest names to /api/outcomes. The stub will reject the language and Harbor will not keep the file.

Do it in-house

Time and a named owner. No vendor. Use the 7-day plan first.

Zero premium — the packet is the product today

Typical Harbor band for this job — advice, not a quote.

Full program

People + system + 90-day proof. Only if the 7-day plan already failed.

Vendor checklist

Score the call. Keep it on this browser.

Weighted questions — yes/no, scale, or text. Must-pass ids persist on this browser. Pass threshold 70. A no on a must-pass is a walk-away — not a maybe.

Brand
Stack shape — not a partnership
  1. property context · weight 2 · must pass

    Can they name your key count and whether you are independent, soft-brand, or major — without a discovery theater?

  2. property context · weight 2 · must pass

    Do they treat your PMS as a shape (Opera-class / Mews-class / Cloudbeds-class) — not a fake partnership slide?

  3. control · weight 3 · must pass

    Who types the status / number — a person, or your product?

  4. vendor · weight 2

    What would have happened anyway in 90 days without you?

  5. vendor · weight 2

    Show a property of this size and stack. Demo-labeled categories do not count as proof.

  6. vendor · weight 2

    What can your agent never do (folio post, mark clean, change a rate)?

  7. vendor · weight 2

    What is the kill-switch if guest comments move?

Does not clear

0 / 100

must_pass: underwrite-verified-outcome-intent-ctx-rooms, underwrite-verified-outcome-intent-ctx-stack, underwrite-verified-outcome-intent-q1

A must-pass failed. Walk away.

How

The brief

The form writes locally. The API stub echoes. Export JSON. That is v1. A licensed desk is a later company problem, not a checkbox on this page.

  1. Step 1

    Fill claim → evidence → caveat → price

    Missing evidence drops the packet to advice or claimed. Harbor will label it.

  2. Step 2

    Export the packet

    harbor-underwriting-packet.json. Keep it with the house. Do not put folio text in it.

  3. Step 3

    Sit a pilot if you want a longer read

    The 30-minute sit on /pilots is how a design partner corrects the how.

  4. Step 4

    Refuse the packet if it reads like a policy

    licensed:false on the same page as the price. A prettier button that implies cover fails the brand.

Tradeoffs

  1. Honest stub

    You get. A file a future underwriter can refuse

    You give. The sentence 'you're covered'

  2. Fake policy UI

    You get. A prettier button

    You give. The brand

Pitfalls

  • · Calling licensed:false a quote.
  • · PII in the packet.
  • · Inventing a loss ratio.

Success criteria

  • · Packet exports with licensed:false.
  • · Evidence level labeled advice, claimed, or verified.
  • · No guest names.

Who

Ranked for this job

Rank is post-job score, then listed order. Not for sale. Software marked demo is an archetype.

Agencies & contractors

Systems

AI agents

Loading the compare table…

Compare

When to pick whom

People do the work beside the desk. Software is a system — demo-labeled when it is a category shape. Agents draft; they do not post money or mark a room clean.

ProviderKindScoreFeePick whenWalk away when
Outcome DeskPeople
8.1
$4–9k packet sitAn owner who will name a price if a criterion holds.Anyone who wants Harbor to issue a policy today.
Caveat Ledger (demo desk)Software· demo
7.5
Demo — not for saleA tech lead who wants the schema on one page.Anyone who wants Harbor to bind cover.
Evidence ScoutAgent
7.8
Draft only — human signsA tech desk that wants a first sentence before the GM edits it.Anyone who wants an agent to close night audit.

Open graph

Hotels on this job

This job is not pinned to a house yet. Open the graph to place it on a building, or the investment desk if the work is a sale file. Harbor will not invent a house.

Evidence

Peer case studies

Nearby jobs