Guest-day pricing model for remote-first startups

What a guest-day means for planning

A guest-day is a way to think about visitor access over a day rather than treating every click as a separate long-term member seat. For a remote-first startup, the useful question is not only “How many people might visit this year?” It is also “How many visitor conversations will be active on a typical day, and which employees need to handle them?”

Separate three populations:

1. **Members:** employees who need a role, presence, queue ownership, or private workspace access. 2. **Guests:** customers, prospects, partners, or other visitors arriving through a reception link. 3. **Occasional participants:** people who join a specific meeting or consultation and do not need permanent internal access.

This distinction keeps a small distributed company from buying a full seat for every person it hopes to serve. It also prevents underestimating the member seats required to respond responsibly. Guest-days describe visitor capacity; they do not replace accountable employees.

The public Kiguri plan signals

Kiguri's public materials reviewed on August 8, 2026 describe a Free plan at $0 for up to eight members, with public reception and visitor links, inquiry forms/basic handoff, member presence or status, three maps, and a stated map-tile allowance. The Business plan is listed at $12 per user per month and includes two guest-days per paid seat every day, AI reception, a response queue and employee handoff, browser phone, longer meetings, and private consultation rooms. Custom pricing is described for higher seat or verified-visitor allowances and additional review or onboarding needs.

These details are planning inputs, not a substitute for the live plan page. Limits, names, and included features may change. Verify the current Kiguri pricing and workspace settings before using the figures in a proposal.

Calculate a starting requirement

Use a simple planning worksheet. First count the employees who need to receive or own visitor inquiries. Do not count every employee if only a customer team needs queue access. Next estimate a typical day and a busy day: number of new visitors, likely simultaneous conversations, and the roles that need to accept a live handoff.

If the Business allowance is still two guest-days per paid seat each day, a team can compare the number of paid seats it genuinely needs with its normal visitor pattern. For example, a startup with four customer-facing seats would plan around the allowance associated with those four seats, then validate whether that covers its real visitor days. The calculation should not be read as a guarantee of capacity for every interaction; it is a prompt to check current product definitions and the team's own usage.

Record the assumptions in plain language: “Four support and sales members need queue access; most visitors are prospects or existing customers; high-volume event days may need a custom review.” This is more useful than choosing a plan from a single monthly traffic number.

Match plan choice to the visitor workflow

Free can be a reasonable way to test a branded reception, visitor links, inquiry forms, basic handoff, presence, and a small map setup when the workspace fits the published allowance. Use the free workflow to learn which visitor purposes occur and whether the team can own the resulting queue.

Business becomes relevant when the startup needs AI reception, a response queue and employee handoff as a repeatable operating process, browser phone, longer meetings, or private consultation rooms. The member count should reflect employees who actually need those capabilities, not a speculative list of everyone who might answer one day.

Custom may be appropriate when visitor volume, verified-visitor allowances, seat count, retention or DPA review, phone requirements, guided onboarding, or priority support need a conversation beyond the standard plans. Describe the requirement and the desired workflow, then ask Kiguri to confirm what is available.

Consider the cost of an unclear handoff

Price is not only the line item. A startup should also consider the operational cost of sending visitors to personal calendars, scattered inboxes, or temporary meeting links. If a guest waits while teammates determine ownership, the team pays in attention and trust. A structured reception and queue can be valuable even when the visitor volume is modest, provided the startup uses the workflow consistently.

Do not claim a specific return, conversion increase, or response-time reduction without measuring your own baseline. Before choosing a plan, review a sample of inquiries and ask which features would change the next action: AI-approved orientation, presence, queue ownership, a private room, or a browser conversation. Buy for a real workflow, not a feature checklist disconnected from how the team works.

Plan for uneven remote-first schedules

Guest-day demand may spike around a product launch, partner event, or customer onboarding window. Separate normal days from known peaks. Write an after-hours message that tells visitors whether they can leave an inquiry, and decide who will review the queue when the normal owner is offline.

If the startup has different regional coverage, use roles and presence to make live handoff language accurate. A visitor should not be promised an immediate answer because one teammate is online in a different time zone but does not own the request. A queued response is better than an uncertain transfer.

Review workspace retention and access as visitor volume grows. More guests mean more context in the queue, so decide who can see it and how long it should remain available. Confirm the current plan's limits, visitor rules, and map allowances before scaling a public campaign.

FAQ

Are guest-days the same as member seats?

No. Member seats are for employees who need workspace responsibilities and access. Guest-days describe visitor usage or allowances according to the current plan definition. Verify the live pricing page for exact terms.

How many seats should a small startup buy?

Start with the employees who need to own inquiries, presence, queue work, or private follow-up. Add seats when a real role requires them, rather than counting every possible future participant.

Is the Free plan enough for a remote-first startup?

It can be a useful starting point when the published member, map, visitor, and handoff limits fit the team's workflow. Confirm current limits and availability before relying on a feature in customer-facing copy.

When should we ask about a Custom plan?

Ask when volume, verified visitors, seats, phone needs, retention or DPA review, onboarding, or support expectations do not fit the standard plan description. Provide the workflow and assumptions so the answer is specific.

Price the responsibility, not just the traffic

A guest-day pricing model helps a remote-first startup separate who works in the virtual office from who visits it. The practical decision combines member ownership, visitor patterns, live handoff needs, private destinations, and honest after-hours operations. Kiguri's public plans provide a starting structure, but the live pricing page is the authority for current numbers and limits.

Review Kiguri pricing and then [explore the customer reception](/) with a short list of your actual visitor intents and responsible teammates.

Sources and further reading

• Kiguri pricing and plan overview • [Kiguri customer reception](/) • Kiguri guides • Kiguri map preview

Sources and further reading

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