Guest-day pricing model for B2B sales teams

Define a B2B guest-day before doing the math

For planning, define one guest-day as one external visitor or buying group creating an active reception interaction on one calendar day. An interaction can include an inquiry to the AI receptionist, a response-queue item, a live handoff, or a follow-up conversation. A person who merely views a public page does not need to count unless the team wants a separate awareness metric.

Write the definition down with sales and finance. A buyer who returns on another day creates another guest-day. Several colleagues can be counted as one buying-group day or separate visitor-days; choose one method and use it consistently. The point is to estimate work, not imitate an unpublished billing term.

Kiguri's customer-facing workflow gives the model a useful shape: a buyer opens a branded link, shares identity, company, and purpose, receives approved answers from an AI receptionist, and may be routed to an available employee. The guest-day count should therefore distinguish a useful sales interaction from anonymous map traffic.

The five numbers a sales team should track

1. Member seats

Members are the employees who operate the virtual reception, receive inquiries, or join buyer conversations. Start with the people who genuinely need access. An engineer who joins one technical call may need a different role from an account executive who owns the queue every day; confirm the workspace permissions and current plan definition instead of assuming every employee needs the same setup.

2. Active guest-days

Count buyer-days that create a meaningful inquiry or handoff. Segment the count by purpose: product exploration, demo, technical evaluation, pricing, partner discussion, and expansion. A purpose breakdown helps explain why 100 guest-days can consume less time than 35 complex evaluations.

3. Human minutes per guest-day

The AI receptionist can answer approved questions and collect context, but an employee remains responsible for discovery, technical judgment, and commercial decisions. Estimate the time to read the context, join, conduct the conversation, and record the next action. Separate a short text answer from a screen-sharing session or a multi-stakeholder video meeting.

4. Live-conversation rate

Measure the share of guest-days that reach a person. Some buyers only need a public answer. Others enter a response queue for follow-up. A live-conversation rate helps the team plan coverage without pretending every visitor should be pushed into a call.

5. Follow-up depth

Count how often a guest-day creates a second meeting, a private consultation, a specialist review, or a procurement task. Follow-up depth is often the most important capacity signal for enterprise sales because the first reception is only the beginning of the evaluation.

Use Kiguri's published plans as the software baseline

The Kiguri pricing section currently describes Free at $0 for up to 8 members, Business at $12 per user per month, and Custom volume pricing. The public information also associates Business with AI reception, a response queue and employee handoff, browser phone, longer meetings, and private consultation rooms. Confirm limits, included channels, and availability at purchase.

These figures describe plans and seats. They do not establish a guest-day price, unlimited visitor capacity, or a claim that visitors become members. Keep three lines in the model:

• **Workspace line:** plan and member seats needed to operate the reception. • **Visitor-operations line:** employee time for buyer intake, conversations, and follow-up. • **Peak-coverage line:** extra coverage for events, launches, partner days, or enterprise evaluations.

This separation makes a comparison more honest. A tool with a low seat price can still require substantial sales time if buyers repeat their context. A useful intake and handoff can reduce avoidable repetition, but it does not make specialist work free.

A worked B2B guest-day example

Imagine a sales team with eight members and 70 active buyer guest-days in a month. Suppose 45 days are early product questions that need an average of 8 employee minutes. Another 20 are discovery conversations averaging 25 minutes. Five are technical evaluations using screen sharing or a private room and averaging 60 minutes.

The estimated human time is:

• 45 × 8 minutes = 360 minutes; • 20 × 25 minutes = 500 minutes; • 5 × 60 minutes = 300 minutes; • total = 1,160 minutes, or about 19.3 employee hours.

The calculation is not a Kiguri invoice. It shows the coverage required behind the reception. Run low, expected, and peak cases. Increase the peak case for a conference follow-up campaign or a partner launch, and test whether the available salespeople can accept the queue without creating a misleading “talk to sales now” promise.

Add a simple context-quality check. If employees still ask every buyer “What company are you with?” and “What are you evaluating?” after the handoff, the intake is not doing its job. If many early questions are answered by approved AI content, the team may reserve live time for conversations that genuinely need judgment.

How guest-days differ by sales motion

Product-led discovery

Product-led visitors may arrive with a narrow question and no meeting expectation. Count the reception interaction and a short answer separately from a qualified discovery call. Keep the public path lightweight so a curious buyer is not forced into a long form.

Enterprise evaluation

An enterprise guest-day can involve a technical owner, a security reviewer, or several stakeholders. The first handoff may be short, but follow-up depth is high. Model private consultation and specialist time rather than averaging the visit with simple product questions.

Partner and channel work

Partner visits may be infrequent but important. Track the account or relationship owner and the preparation time before a conversation. A branded visitor link can make the arrival recognizable while the commercial notes stay in the team's normal process.

Expansion conversations

An existing customer discussing additional teams has different context from a new prospect. Count the guest-day, then record whether the conversation needs an account owner, a plan explanation, or a technical review. Do not use visitor volume alone as a forecast of expansion revenue.

Questions to ask before adopting a pricing model

Confirm whether the vendor's current quote is based on members, visitors, usage, or a combination. Ask what “user” means in the order form and which conversation modes your plan includes. Verify how response-queue items, guest access, maps, and private rooms work for your intended workspace. For a high-volume deployment, ask how Custom volume pricing and any verified-visitor allowances are calculated.

Compare the operational model, not only the sticker price. Does reception capture company and purpose? Can an employee receive context without restarting discovery? Can the team show honest availability and move to a richer channel when staffed? These answers determine whether guest-days are manageable.

Measure the model after launch

Review guest-days by purpose each month, along with live-conversation rate, human minutes, reassignment, and follow-up depth. Read a sample of handoffs. Remove questions that never change routing and improve answers for questions that recur. Keep a note of plan and pricing changes so a forecast does not quietly rely on an older public page.

Frequently asked questions

Does Kiguri publish a guest-day price?

The public pricing information reviewed for this guide lists member-based plans: Free at $0 for up to 8 members, Business at $12 per user per month, and Custom volume pricing. It does not establish a separate guest-day meter. Confirm current billing terms with Kiguri before purchase.

Does every buyer need a paid member seat?

Not automatically. A member operates the workspace; a visitor is an external person arriving for a conversation. Confirm current plan definitions and permissions for the workspace rather than treating the two as identical.

Can an AI receptionist reduce the human cost of guest-days?

Approved answers and focused intake can reduce repeated explanations and unnecessary handoffs. They do not remove the need for employees to conduct discovery, technical review, or commercial decisions.

How should a sales team model an event spike?

Create a peak scenario with the expected guest-days, live-conversation rate, and specialist minutes. Confirm who is available, what the offline path says, and whether a response queue can preserve context after the event.

Where can I verify current Kiguri pricing?

Use the Kiguri pricing section and confirm the offer when purchasing. Prices, limits, and availability can change.

Sources and further reading

• [Kiguri customer-facing virtual office](/) • Kiguri pricing • Kiguri AI receptionist for B2B sales teams • Kiguri shared response queue guide • Kiguri Guides

Sources and further reading

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