I am self-managing a Cincinnati condo on Airbnb and trying to figure out where the actual time goes before I decide whether to keep doing it myself

The 10pm towel bar call lands wherever the contract says it lands, and most co-host agreements do not specify clearly enough to matter when it is 10pm.

Take a co-host charging 15 percent of your $2,300 gross, so $345 a month. At your 25 to 35 hours, that is roughly $10 to $14 per hour of your time bought back, which undercuts your consulting rate badly unless they actually absorb the high-friction hours, not the easy ones. The typical split in practice is that a co-host handles the guest messaging queue and cleaner coordination, but emergency calls default to the owner unless the agreement explicitly creates an on-call obligation with a defined response window. Ask any candidate: what happens at 10pm when a guest cannot enter? If the answer is anything other than "we call the locksmith and tell you after," the friction stays with you.

Pricing authority is the sharper question. Co-hosts who take pricing off your plate entirely tend to optimize for occupancy over rate, because their fee is a percentage of revenue and a filled night at $95 beats an empty one at $115 for them even when the math runs the other way for you. If you keep PriceLabs access and they execute inside parameters you set, you retain rate integrity but you do not actually recover the time the pricing work costs you now.

The tasks you have not mentioned are the ones worth mapping before you decide: guest review responses, listing copy updates when a comp changes positioning, and supply restocking when a cleaner flags a shortage. Those three either stay with you or vanish depending on how the scope is written, and most co-hosts treat them as owner tasks by default.

What does your consulting work look like in terms of scheduling? Specifically, whether the 25 to 35 hours are eating predict

The task split depends almost entirely on how you draft the co-host agreement, but in practice most co-hosts operate one of two ways: full operational authority, where they own every guest-facing moment including the 10pm call and you only hear about it in a weekly summary, or a lighter arrangement where they handle messages and coordinate cleaners but emergencies escalate to you because the co-host is not carrying liability for a judgment call on your property. The second model is more common among part-time co-hosts and local operators who manage a handful of units, and it is the one that still costs you 8 to 12 hours a month. On pricing, the cleaner picture matters here: a co-host who also controls your calendar has a direct incentive to keep occupancy high, which can mean undercutting on rate to fill gaps, so if your PriceLabs work is protecting RevPAR rather than just filling nights, you want to define in writing whether they can override minimums and by how much. At $112 average and 68 percent occupancy your RevPAR is around $76, and a co-host who buys occupancy at the cost of rate could push that lower even while the calendar looks fuller. The question I would want answered before signing anything is whether they charge a flat monthly fee or a percentage of revenue, because that structure determines whether their incentives are aligned with yours on rate.

Co-hosts vary wildly but the 10pm call going to them is the whole point of paying 20-25%.

What I would nail down first: does their contract give them pricing authority up to a ceiling you set, or do they ping you for every move above some threshold?

The assumption doing the most work in your framing is that a co-host relationship is a binary where you either hand over a task or you keep it. In practice the 10pm keypad call is a good stress test for this. A co-host with a vendor network and a scripted response protocol absorbs that call completely, meaning the guest reaches them, they reach the locksmith or the backup key holder, and you see a message in the morning. A co-host who is essentially a message-forwarding layer will triage it, decide they cannot authorize a $150 emergency locksmith call without your sign-off, and you are back on your phone at 10pm anyway. The contract has to specify a spending authority threshold, something like "co-host may authorize emergency repairs up to $200 without owner approval," or the task never actually leaves you. That threshold is the thing most people do not negotiate explicitly and then wonder why they are still getting woken up.

Pricing authority works the same way but the stakes are different. Most co-hosts will operate PriceLabs or a comparable tool themselves and will want approval rights for anything that deviates from agreed floor and ceiling prices, not for every individual adjustment within that band. So in a well-structured arrangement you set a floor, a ceiling, and perhaps a minimum stay rule by season, and they move freely inside that box. The twice-a-week manual review you are doing now gets replaced by a conversation once a month about whether the box still fits the market. Where this creates tension is that your floor price is also their floor commission, so a co-host who takes 20 percent has a mild incentive to push occupancy over rate, which at $112 average and 68 percent occupancy is worth checking: your RevPAR is around $76, and whether a co-host's pricing philosophy would push that number up

The guest emergency question is the one worth locking in writing before anything else, because co-hosts handle it inconsistently and the gap between "we manage all guest communication" and "we are available 24/7 for emergencies" is where owners get burned at 10pm anyway. A co-host who absorbs messaging, turnovers, and the cleaner-cancels scramble is probably worth 15 to 20 percent of gross on a unit like yours, so call it $345 to $460 a month at your current numbers, and that math pencils if those 25 to 35 hours genuinely free up to consulting work, but only then. On pricing authority, the practical split that works best is you set the floor and ceiling in PriceLabs, the co-host or the tool moves within that band without approval, and you review once a week rather than approving every adjustment, which removes the bottleneck without handing over full control. The thing worth confirming before you sign anything is whether the co-host carries their own liability coverage or whether a guest injury during a turn they coordinated lands on your homeowner policy.

What does your condo association say about short-term rentals, and does Cincinnati's registration requirement affect your Northside unit specifically? That shapes whether a co-host can even operate under their own name or whether everything has to run through you as the licensed owner of record.

The 10pm keypad call lands on you until you give the co-host explicit authority to dispatch a locksmith and spend up to some agreed dollar amount without waking you, so the contract needs a spending threshold, not just a list of responsibilities, because that number is where real delegation actually happens.

On pricing, most co-hosts will take over PriceLabs operation entirely if you want them to, but the ones worth working with will ask you to set floor prices and blackout dates at the start and then leave them alone, and if a co-host wants your approval twice a week they are charging you for a job they are not doing.

What does your current monthly net look like after cleaning and supplies but before your time, and do you have a sense of what a Cincinnati co-host in that market is quoting for commission on a unit at your occupancy level?

You have done the work here that most owners skip, so I can give you a more direct answer than usual.

A co-host's scope varies by agreement, but the standard arrangement covers guest communication, cleaning coordination, and the 10pm keypad call. That last one goes to the co-host, not you, because you are paying for the operational layer. If you are still fielding emergencies yourself, the co-host is not doing the job. Ask any candidate directly: "Who picks up when a guest cannot get in at midnight?" The answer tells you a lot.

Pricing authority is genuinely negotiable. Some co-hosts want full control because their revenue optimization is part of what justifies the fee. Others will run a tool like PriceLabs and check in with you on weekly minimums or seasonal floors. Neither is wrong, but you need to decide how much of that you want to keep before the conversation starts. If you hand it over entirely, make sure the agreement specifies that the co-host carries pricing risk, meaning they are accountable for results, not just execution.

On your math: at $2,300 gross and a 20% co-hosting fee, you give up roughly $460 a month. Your cleaner stays on your books unless the co-host has their own cleaning network, which many do at similar rates. Supplies usually stay with the owner too. So the real question is whether $460 buys back enough of those 25 to 35 hours to matter to you, given that you said you are not turning down consulting work to fill them.

One thing worth confirming with a local short-term rental attorney or your city's planning office: Northside has seen some shifting permit language in the last year, and a good co-host should already know your compliance status. That regulatory knowledge is part of what you are buying.

What does your current occupancy look like in your slower months, say November through February? That affects how compelling the fee math looks across a full year.