Guest-day pricing model for partner offices

What is a guest day?

For planning, define one guest day as one guest’s active visit during one calendar day. A two-day workshop with five guests creates 10 guest days. A single guest who joins a morning briefing and returns for an afternoon session still counts as one guest day under this model.

This definition is deliberately operational. It helps a team estimate traffic, staffing, and event effort without suggesting that Kiguri bills by that measure. Write the definition at the top of the spreadsheet or planning note so marketing, operations, and finance use the same denominator.

Use these inputs:

• **Guests per day:** the number of external visitors expected on a typical active day. • **Active days:** the number of days the partner reception is open for the activity. • **Guest days:** guests per day multiplied by active days. • **Internal members:** partner-office employees who need to configure, monitor, or host visits. • **Planning period:** the month or event window being compared.

The model should keep guest volume separate from member licensing. Visitor traffic may influence staffing and invitation design, while the public plan reference is tied to members and plan level.

Public pricing anchors

At the time this draft was prepared, Kiguri’s public pricing references were:

• **Free:** $0, up to 8 members. • **Business:** $12 per user per month. • **Custom:** volume pricing for larger or specialized requirements.

These are the only Kiguri prices used in the examples below. Taxes, payment fees, implementation work, optional services, discounts, and negotiated terms are not included. Pricing and limits can change, so confirm the live [Kiguri pricing information](#pricing) before approval.

The planning formula

The basic model is:

**guest days = guests per active day × active days**

To compare a plan reference with an event, first estimate the monthly member cost using the public plan anchor, then divide that planning cost by guest days. This produces an **illustrative cost per guest day**, not a Kiguri charge:

**illustrative cost per guest day = monthly plan reference ÷ guest days**

For Business, the monthly plan reference is:

**internal members × $12**

Only count members who require Business access in the scenario. If the workspace remains within the public Free allowance of up to 8 members, the plan reference is $0 under this simple model. That does not mean the event has no cost: staff time, preparation, support, and any unrelated services still matter.

Scenario A: a small partner workshop

Imagine a partner office with 6 internal members hosting 4 external guests for 2 active days.

• Guest days: 4 × 2 = 8. • Internal members: 6. • Public Free plan reference: $0 because the member count is within the stated allowance of up to 8 members. • Illustrative plan cost per guest day: $0 ÷ 8 = $0.

That result should be read carefully. It means the public plan reference contributes no subscription amount in this simplified comparison. It does not value the host’s time or guarantee that every desired capability is available under every configuration. The team should still test its reception, intake, queue, and handoff workflow before inviting clients.

Scenario B: a launch week with more hosts

Now consider 12 internal members supporting 10 guests per day for 5 active days.

• Guest days: 10 × 5 = 50. • Internal members: 12. • Business plan reference: 12 × $12 = $144 per month. • Illustrative plan cost per guest day: $144 ÷ 50 = $2.88.

The $2.88 figure is a planning ratio for this scenario. It is not a per-guest invoice and it should not be compared directly with a published guest-day product. It simply lets the team see how the same member plan is spread across a busier event window.

If the same 12-member workspace hosted only 5 guest days, the ratio would rise to $28.80. That does not mean Kiguri became more expensive per visitor; it means a fixed monthly member reference is being allocated over fewer visits.

Scenario C: recurring partner reception

Suppose 10 internal members operate a reception every weekday for a 20-day planning month, with an average of 3 guests per day.

• Guest days: 3 × 20 = 60. • Business plan reference: 10 × $12 = $120 per month. • Illustrative plan cost per guest day: $120 ÷ 60 = $2.

This scenario can be useful when comparing a continuous reception with a short event. The office may decide that a recurring public entrance is valuable even when daily traffic varies, because the reception gives every partner a consistent way to explain a request and reach the right employee.

What the guest-day ratio leaves out

Do not use the ratio as the only approval metric. Add operational questions alongside the arithmetic:

Host coverage

Who watches the response queue? If no employee is available, what message and follow-up path will the visitor see? A low subscription ratio does not make an unstaffed reception a good guest experience.

Conversation complexity

A short information request and a multi-hour implementation workshop are both guest days, but they consume very different host effort. Estimate expected handoff time separately.

Privacy and access

Partner visitors may need a private room, screen sharing, or account-specific context. Confirm the current workspace configuration and access boundaries before promising a channel or destination.

Seasonality

Launch weeks, events, and renewal periods can produce different traffic. Model a quiet month, a typical month, and a peak month rather than relying on one average.

Plan fit

The public Free allowance is based on members, not guest-day volume. If the team needs a larger member group or specialized volume terms, ask Kiguri about Custom pricing rather than inventing a guest surcharge.

How to build a useful planning sheet

Create one row per scenario with columns for period, internal members, guests per day, active days, guest days, public plan reference, and illustrative cost per guest day. Add non-price columns for queue coverage, expected handoff time, privacy level, and owner.

Keep a separate note for assumptions. For example: “Guest day means one external visitor on one calendar day; Business reference uses $12 per user per month; no taxes or negotiated terms included.” This prevents a future reader from mistaking the ratio for an invoice.

Review the sheet when the public pricing page changes, when the member count crosses the Free allowance, or when the partner workflow adds a new requirement. A current assumption is more useful than a precise calculation built on an old plan.

Frequently asked questions

Does Kiguri publish a guest-day price?

No guest-day fee is used in this guide. Kiguri public pricing is referenced by member plan: Free at $0 for up to 8 members, Business at $12 per user per month, and Custom volume pricing. Confirm current terms before purchasing.

Is the $2.88 example a quote?

No. It is an illustrative allocation of a $144 monthly Business plan reference across 50 guest days. It is not a per-visitor charge, promise, or official Kiguri billing metric.

Can guest volume change the plan automatically?

Do not assume that it does. The public references used here describe member limits and plan levels. Ask Kiguri how your workspace, member count, and intended visitor workflow are handled.

Should staff time be included?

Yes. Add host coverage, preparation, follow-up, and any event support as separate operational costs. The plan ratio only provides a narrow subscription comparison.

When should a partner office ask about Custom pricing?

Ask when the workspace is larger than the public Free allowance, needs volume terms, or has requirements that the public plan summary does not answer. Use the current Kiguri pricing conversation for a tailored answer.

Sources and further reading

• [Kiguri customer-facing virtual office](/) • [Kiguri pricing and plan information](#pricing) • Kiguri security information • Kiguri guides

Use guest days as a shared planning language, not as a substitute for Kiguri’s actual pricing terms. Anchor the calculation to public member-plan references, label every ratio as illustrative, and verify the live plan details before a partner office commits to an event or recurring reception.

Sources and further reading

Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.