01
The hotel list
Every hotel your group owns on one list, with a page per hotel: who runs it, what is due, what is open, and what came in this week.
Your hotels' weekly numbers,
contracts, and documents.
One workspace, not a scavenger hunt.
One workspace for the hotels your group owns: contracts, documents, contacts, and the weekly numbers, on one page per hotel. I build it and I keep it running.
1. Every hotel on one listA page per hotel: who runs it, what is open, what came in this week.
2. Documents with dates on themContracts, insurance, licenses, and vendor files attached to the hotel they belong to.
3. One weekly number per hotelStaff submit in a short form. The portfolio view keeps the missing hotels visible.
What you get
One workspace, one page per hotel.
02
Contracts and documents
Contracts, insurance, licenses, and vendor documents in one place, with renewal dates attached to the hotel they belong to.
03
The people at each property
General managers, owners, and the vendor contacts your office keeps using, in one place instead of spread across inboxes.
04
The weekly numbers
Each hotel submits its numbers in a short form or a template. The portfolio view keeps the hotels that have not sent theirs visible, and the weekly report exports instead of being rebuilt.
Who this is for
A group that collects numbers from each hotel by hand.
HOTELS
A hotel management or ownership group with roughly three to thirty owned hotels.
NUMBERS
Weekly or monthly numbers come from each property by hand, across email, texts, spreadsheets, and however each general manager likes to send them.
OWNER
One person in operations owns that collection, and it takes a day of their week.
OFFICE
Contracts, insurance, and licenses live in different inboxes, and renewal dates are tracked from memory.
Proof from a real workspace
A property portfolio workspace with one owner.
BladeAIUI is the workspace I build and run today. It replaced a scattered operating picture with one supportable property workspace: portfolio records, contracts, documents, contacts, and follow-up meeting in the same queue instead of being reconstructed across separate tools. It runs a property portfolio, and the shape of the work is the same as this offer: a page per property, documents with renewal dates on them, and recurring numbers that land in one view.
PROPERTY OPERATIONS
Before
Portfolio records, contracts, documents, contacts, and follow-up lived in separate tools. Operators could get the answer, but they had to stitch it together by hand.
Built
A React and TypeScript workspace with an Express API, SQLite data layer, and import paths for legacy files and operational records.
After
The team works from one portfolio queue and can open the property, contract, document, contact, or financial context from the same task.
One property queue Linked operational records Ongoing technical ownership
How engagements start
A written scope, then dates you can hold me to.
Every conversation starts with a no-cost fit call. If the work makes sense, you get a written scope with the dates and the price before anything begins.
01 · START
Scope, sign, start
Send the list of your owned hotels and the name of the person who collects the weekly numbers. You get a written scope with dates and the price. Signing starts the clock.
02 · MIDPOINT REVIEW
You use it at four weeks
The entry engagement reaches a working review at four weeks. You use the workspace, say what is wrong, and I fix it before the end date.
03 · ACCEPTANCE
Live at eight weeks
The workspace goes live at eight weeks from the start. When you accept it, warranty covers 45 days, and hosting and support continue month to month after that.
Start here
Book a hotel ops fit call.
Leave knowing what happens next.
The first call is a fit check. Bring the hotels you own and how the weekly numbers reach you today, and you will know whether this is worth starting.