Technology & Services World 2026

Why Technology and Services World 2026 centers on the AI customer lifecycle

Technology and Services World 2026 opens on October 19 and closes on October 21, 2026 in Las Vegas. TSIA lists 80+ sessions across 3 AI lifecycle tracks, so the programme is organized around operating the customer lifecycle rather than a general technology expo.

For a revenue team, the useful framing is not simply conference scale. The three tracks create separate preparation lanes for lifecycle architecture, AI monetization and autonomous customer experience. Account lists, meeting hypotheses and session choices should be tagged to one of those operating questions before travel.

The page is therefore best used as a planning brief for customer-lifecycle conversations. It should not be treated as a substitute for the organiser agenda, because session times and room assignments can change as the programme matures. Recheck the official schedule immediately before booking internal coverage.

Which technology services leaders belong in the room

The published audience begins with Go-to-market and sales leaders. It also names customer success, services, support and professional services leaders, while the subject list spans AI economics, services profitability, pricing, customer lifecycle transformation and operational scale for teams responsible for durable customer value.

The role mix spans commercial ownership and post-sale delivery. A sales leader may attend to understand pricing or expansion, while customer success and services leaders may focus on adoption, margin and scalable delivery. Shared account notes should make those different motives visible instead of reducing every attendee to one persona.

Product and operations teams are relevant when they influence how AI-enabled services are packaged, delivered or measured. Before outreach, identify the operating responsibility behind the title, the customer-lifecycle stage it affects and the proof the contact would need to justify a next meeting.

What the published October calendar confirms and leaves open

The current event page establishes an October 19 opening, an October 21, 2026 close and 3 full days. As of September 24, 2026, the reviewed agenda and registration pages do not publish a complete daily timetable or expo opening and closing hours, so an hour-by-hour calendar would be unsupported.

Build the internal calendar around confirmed access, not assumed expo hours. Use Monday for pass-specific workshops, meetups and the reception, then reserve Tuesday and Wednesday for the main programme described in the pass inclusions. Leave unscheduled buffers until the organiser publishes a complete timed grid.

Each attendee should carry a short priority list rather than an overfilled diary. Mark keynote commitments, target-account meetings and one learning objective per track first. Only then add opportunistic conversations, because transit inside the venue and unplanned follow-ups will consume time that a provisional schedule cannot predict.

How the three conference days divide by access

Full Access starts Monday with Meetups, Expert-led Workshops and the Welcome Reception. Limited Access begins with a half-day Monday programme, while both pass descriptions place keynotes, breakouts, expert sessions, networking and expo access on Tuesday and Wednesday. That distinction should shape each attendee's calendar.

Full Access is the practical choice when Monday workshops and meetups are part of the objective. Limited Access still includes the Monday half day and the main Tuesday-Wednesday programme, so it may fit attendees whose goal is concentrated networking, keynotes and selected breakouts rather than the complete workshop experience.

Do not compare the passes only by price. Compare the access each role needs, the meetings already confirmed and the learning that must be brought back to the team. A lower-cost pass that excludes a critical working session can create more friction than the apparent saving.

What is confirmed about the ARIA conference footprint

TSIA confirms ARIA Resort & Casino in Las Vegas, NV as the venue for the 3-day conference. The reviewed 2026 pages do not identify meeting-room names, an expo hall, registration-desk location or a downloadable floor plan, so the physical footprint cannot be described more narrowly.

ARIA being both hotel and event venue reduces the number of external transfers, but it does not remove on-property walking time. Until a floor plan is published, allow buffer between sessions and meetings and use a single, unmistakable meeting point for contacts who do not yet have a room assignment.

Once the organiser releases room names or a map, update the team brief rather than rewriting account priorities. Add the exact room, nearest landmark and expected travel buffer to every meeting. That operational layer prevents a strong account plan from failing because two people interpreted a venue label differently.

Which Las Vegas travel details remain unpublished

The official pages place the event in Las Vegas, NV at ARIA Resort & Casino and use September 16 as the room-block threshold. They do not publish an airport transfer, parking rate, transit route or conference shuttle schedule as of September 24, 2026.

Travel planning should stay separate from event claims. The official pages verify the Las Vegas venue and room terms, but they do not currently verify airport timing, parking or shuttle operations. Use the hotel and transport providers for those details and keep any estimate labelled as a planning assumption.

A resilient itinerary leaves margin before the first required programme item and after the last confirmed commitment. Team members should share arrival details, hotel confirmation and an escalation contact in one travel sheet. Refresh it when flights or organiser timings change instead of copying stale logistics into outreach notes.

How the four pass prices and group discounts compare

Standard pricing lists $3,150 for Full Access and $2,100 for Limited Access; the member Full Access price is $2,850. Groups registering by October 12, 2026 receive 20% Off for teams of 5 to 14, with higher reductions for larger groups.

The published prices provide a defensible registration baseline, not a complete event budget. Add travel, lodging, meals and any approved sponsorship or activation expense only when an owner can point to a current quote. Keep member, standard and group assumptions in separate rows so later changes remain traceable.

For group registration, validate headcount before applying the organiser's discount bands. A team can also record which pass each person needs, because headcount alone does not establish the correct total. A source date in the budget note keeps unquoted exhibit costs from appearing as settled spend.

Which registration, payment and transfer rules apply

The FAQ allows a refund minus processing fees before the stated cancellation deadline. Payment uses major credit cards or approved invoicing options, and a registration may be transferred to another attendee within the same organization before the event. A designated owner can retain the confirmation and invoice trail.

Registration administration is a small but consequential workstream. Store the attendee name, pass type, payment status, invoice or receipt, and the organiser confirmation in a shared location. If staffing changes, use the documented transfer path rather than buying a replacement before eligibility has been checked.

Cancellation decisions should reference the current terms and their deadline, since a summary cannot capture every condition. Assign one person to monitor the roster and resolve exceptions with the organiser. That creates a clear audit trail and prevents a last-minute substitution from becoming an untracked access problem.

What the ARIA room block includes after September 16

ARIA Resort & Casino is the conference hotel and venue. After September 16, rooms move to prevailing rates, with a cited 10-20% saving for attendees and a discounted resort fee of $39 per night while inventory remains. Availability remains the practical constraint.

The room-block threshold matters because the economics change after it. Keep the room rate, resort fee, taxes and cancellation terms as separate budget lines, and retain the confirmation from the booking channel. A percentage saving is not a guaranteed nightly rate and should not be entered as one.

If the discounted inventory is unavailable, compare alternatives on total trip friction as well as nightly cost. Staying off property can add transport time and reduce the ability to use informal meeting windows. Any alternative should therefore include a realistic transfer buffer without attributing that estimate to TSIA.

Why arrival and departure times cannot yet be calculated

The date range runs from October 19 through October 21, 2026 in Las Vegas, NV. The reviewed sources do not supply the first required arrival time, final programme close, airport transfer duration or exhibitor move-in window, so a defensible arrival and departure calculation is not yet available.

Arrival and departure choices should follow confirmed commitments. Until the complete timed schedule exists, avoid promising a flight connection immediately after a presumed closing session. Protect time for the first priority meeting, the final committed conversation and travel between the room, luggage storage and transport pickup.

The team brief can distinguish confirmed times from provisional holds with simple status labels. That prevents an estimate from being repeated as an organiser fact. Revisit the calculation when the final agenda, workshop assignments and any exhibitor obligations become available from the official event channels.

How TSIA organizes the 2026 sponsor field

The current sponsor page separates Diamond Sponsors, Platinum Sponsors and Gold Sponsors. It also displays Silver Sponsors and Spotlight Alley Sponsors as distinct levels, but company names are presented visually rather than in the text snapshot used for this refresh.

Sponsor levels show the commercial structure of participation, but they do not identify every company in text that can be reliably mapped here. Treat the official sponsor page as the live directory. Capture company names only when they are visible and current, then match them to the team's account system.

The useful output is a short, owned account list with a reason for each meeting. Separate customers, open opportunities, partners and net-new prospects. That gives representatives a decision rule when the floor is busy and prevents sponsor prominence alone from substituting for account relevance.

Why the current sponsor directory is not a booth map

TSIA publishes Diamond Sponsors and Platinum Sponsors groupings plus a Spotlight Alley Sponsors category. The reviewed 2026 pages do not provide a searchable company directory, booth numbers, product filters or an expo map, so those sponsor groupings cannot serve as a reliable booth sequence.

Without booth numbers or a searchable directory, no responsible route can claim to identify the first booths to visit. The team can still prioritize known accounts before arrival, but the physical sequence must wait for the official floor information or be adjusted on site from visible locations.

When a current map appears, connect each target to a location and cluster nearby conversations. Preserve a separate high-value list so route efficiency never outranks account importance. If a sponsor cannot be verified, record it as an open research item instead of guessing a booth or product category.

Which five announced keynotes frame the programme

The announced keynote roster includes J.B. Wood, Thomas Lah and Sanjay Kulkarni. George Humphrey and Bernard Slowey add TSIA research and Salesforce customer-success perspectives to the same programme. Together, those perspectives cover strategy, research, delivery, adoption and measurable customer outcomes.

The keynote list gives the team named programme anchors with different operating viewpoints. Use those sessions to refine questions rather than to produce generic social posts. A pre-event note should state which account hypothesis or lifecycle decision each keynote might help a representative test.

After each keynote, capture one implication, one affected account and one follow-up action. That compact format turns programme learning into revenue-team context without pretending the speaker endorsed a product or commercial position. Speaker titles and session details should be rechecked on the official agenda before publication.

Why exact meeting windows are not ready for booking

Monday access includes Meetups, Expert-led Workshops and the Welcome Reception. The official agenda does not yet attach start and finish times to those blocks, and Tuesday and Wednesday lack a complete timed grid, so bookable meeting windows cannot be totaled from current evidence.

Available meeting inventory cannot be calculated until timed programme blocks are published. For now, classify Monday commitments by pass access and protect Tuesday-Wednesday anchor sessions. Add customer meetings only where there is an explicit buffer, and do not convert an untimed agenda label into a precise availability claim.

When the schedule is complete, calculate windows per attendee rather than across the whole team. Two people can cover different tracks, but neither can be double-booked. Keep travel time, preparation and note capture in the calendar so the apparent number of slots does not exceed workable capacity.

Who the AI lifecycle programme is designed to serve

Technology and Services World names Go-to-market and sales leaders alongside customer success, services, support and professional services roles. Its topic set covers AI economics, services profitability, pricing strategy, customer lifecycle transformation and operational scale, which narrows the fit to teams working on those operating questions.

The highest-fit account is one whose active priorities intersect the published subject areas. That could mean AI service economics, professional-services margin, pricing, customer adoption, support transformation or operating scale. Fit should be evidenced by known account context, not inferred solely from an attendee's title.

Score targets with a small set of observable inputs: lifecycle problem, strategic timing, relationship strength, likely decision role and a useful next step. Record the evidence next to the score. That keeps prioritization explainable and reduces the tendency to send the same undifferentiated message to every attendee.

How to narrow an account list without a floor directory

The published buyer language starts with Go-to-market and sales leaders. TSIA also divides commercial participation into Diamond sponsor levels and Spotlight Alley, which distinguishes established sponsorship from a smaller showcase format. Without a current company directory, account selection must remain tied to known customer and opportunity records rather than inferred booth occupants.

Start with the company's own customer and opportunity records, then use verified event participation as a signal. Sponsor level can help indicate presence, but it does not reveal buying intent. Every named target should have an account owner and a concise reason that is specific to its current situation.

Separate research confidence from outreach priority. A high-priority account with incomplete event evidence requires verification, while a clearly listed sponsor may still be commercially irrelevant. This distinction helps the team act quickly without turning the sponsor hierarchy into an unsupported ranking of purchase likelihood.

What the current pages say about an event app

The event covers 3 full days and advertises 80+ sessions, with Most sessions recorded for registered attendees after the conference. The reviewed pages do not name a 2026 mobile app, planner vendor, messaging tool or reservation workflow, so no app feature can be attributed to this edition.

Recorded sessions may extend learning after the conference, but the official material reviewed here does not establish an event-app workflow. Plan meeting coordination through tools the team already controls, and treat any future organiser app as an optional operational layer once its current features are verified.

A simple shared calendar, account brief and note standard can cover the essential work without making claims about an unknown platform. If TSIA later announces scheduling or messaging features, test access and permissions before depending on them for a customer meeting or an important handoff.

Why the planner and capture workflow cannot yet be compared

The sponsor structure includes Diamond Sponsors and Spotlight Alley Sponsors participation, and Most sessions are recorded. None of the reviewed current pages names a show planner or exhibitor lead-capture product, so the boundary between agenda planning and contact capture cannot be compared without inventing tooling.

Agenda planning and conversation capture solve different problems. The former determines where a representative intends to be; the latter preserves what happened, why it matters and what comes next. No current evidence supports assigning both jobs to a specific organiser tool for this event.

The safe operating model is to keep the official schedule as the source for programme changes and use the team's approved system for account notes and follow-up. If a 2026 planner or scanner is later documented, evaluate its fields and exports before changing that division of responsibility.

What is known about pass cost but not sponsorship space

Attendee pricing is published at $3,150 for standard Full Access, $2,100 for Limited Access and $2,850 for member Full Access. The 2026 sponsor page does not publish package prices, booth-space rates, service charges or an exhibitor rate card, so those attendee figures cannot stand in for exhibit cost.

Registration cost is not exhibit cost. A complete exhibitor budget may include sponsorship, space, services, travel, lodging, production, freight and staff time, but each amount needs a current quote or approved internal record. This page intentionally leaves unverified line items open.

Create a budget worksheet that separates committed, quoted and estimated amounts. Preserve the date, source and owner for every number. That structure makes later ROI analysis possible without manufacturing a return figure from attendee pass prices or from a sponsorship package that is not publicly priced.

Why staffing math must wait for expo hours

TSIA describes 3 full days, 80+ sessions and 3 AI lifecycle tracks. The reviewed sources do not provide expo floor hours, a booth size or a conversation target; staffing and coverage arithmetic therefore remains unavailable rather than being filled with a generic rep count.

Staffing should follow coverage obligations rather than a generic event formula. Assign owners for priority meetings, sessions, sponsor duties and note quality, then check for conflicts. Until expo hours and the activation footprint are known, a precise representative count would create false certainty.

Once current operating hours and booth requirements are available, calculate simultaneous coverage and add breaks, transitions and follow-up time. Keep one accountable lead for changes. The goal is not maximum headcount; it is enough prepared capacity to execute the verified plan consistently.

What current evidence says about official lead capture

The current sponsor page documents Diamond Sponsors, Platinum Sponsors and Gold Sponsors participation levels. After checking the event home, pricing, FAQ, agenda, networking, sponsor and registration-terms pages on September 24, 2026, no current lead-retrieval vendor, order form or device price was verified for this edition.

Because no current scanner product or price is verified, the page does not name a vendor. Exhibitors should obtain the 2026 order form or written organiser guidance before budgeting hardware, licences or exports. A prior-year product should not be carried forward as if it were current.

The evidence checklist is straightforward: vendor name, ordering channel, deadline, package contents, user or device limits, field schema, offline behaviour, export format and CRM path. Record the source for each answer. Any missing item remains a procurement question, not a prompt for invented detail.

Which capture fields and export limits remain undocumented

The sponsor page also distinguishes Diamond Sponsors, Silver Sponsors and Spotlight Alley Sponsors participation. None of the reviewed 2026 material states which badge fields a scanner returns, whether notes work offline, how many users share a licence or which export and CRM options are included.

A useful capture workflow needs more than a scanned identity. It should preserve the account, contact role, business problem, timing, decision context, agreed action and owner. Whether an organiser product supports those fields cannot be stated until current documentation is available.

Before selecting a tool, test the full path from conversation to the system of record. Check consent, offline behaviour, duplicate handling, exports, enrichment boundaries and owner assignment. The evaluation should use the team's actual fields and security requirements rather than a generic feature list.

Why no named scanner comparison is supportable yet

TSIA's current commercial hierarchy includes Diamond Sponsors, Platinum Sponsors and Spotlight Alley Sponsors categories. Because no 2026 scanner product is proven at level 1 or level 2, a named vendor comparison would be speculation; the structured comparison therefore keeps the organiser side as On your own.

There is no evidence basis for a named scanner-versus-platform comparison on this page. The organiser side therefore remains an evidence gap, while the B2Brain column describes approved capabilities. This avoids turning an unknown event service into an inaccurate competitive claim.

When official documentation is obtained, compare outcomes and constraints on the same dimensions: capture speed, contextual fields, offline use, exports, integrations, follow-up routing and total cost. Keep verified facts separate from internal preference so the final choice can be reviewed by operations and security.

What is missing before choosing one capture workflow

The known attendee prices are $3,150, $2,100 and $2,850 for the published pass combinations. A capture-workflow choice still lacks an official vendor price, order deadline, device limit, export format and integration specification, so the evidence does not support choosing one tool or a combined setup.

Tool choice depends on the operating requirement. A team that only needs organiser-compliant identity capture may make a different decision from one that needs account context, meeting commitments and immediate routing. The current evidence is insufficient to price or validate the organiser option.

Document the minimum workflow first, then ask vendors to demonstrate it end to end. Include the failure path for lost connectivity, duplicate records and missing consent. Make the decision after current pricing and data-handling terms are available, not from a feature assumption copied from another conference.

Which conversation fields match TSIA's buyer roles

The buyer list names Go-to-market and sales leaders plus customer success, services, support and professional services roles. The Architecting the AI-driven lifecycle track adds operating-model and organization context, making role, lifecycle stage, current process, outcome proof and next step the event-specific fields worth preserving.

The recommended fields reflect this conference's cross-functional audience. A useful note connects the attendee's function to a lifecycle stage, operating problem, commercial impact, decision role and next action. That creates context a follow-up owner can understand without relying on memory from the floor.

Keep the form short enough to complete during or immediately after the conversation. Use controlled values only where they improve routing, and leave space for a concise evidence note. Do not infer sensitive or unavailable attributes merely to fill every field; accuracy is more valuable than completeness theatre.

How the programme scale changes lead quality decisions

The organiser positions the conference as 3 full days with 80+ sessions across 3 AI lifecycle tracks. That breadth makes a badge count insufficient on its own: lead quality depends on matching a conversation to the attendee's function, lifecycle problem, decision role and agreed follow-up.

Measure quality at the account and next-step level. Useful counts include conversations tied to target accounts, contacts with a verified role, agreed meetings, accepted follow-up owners and completed handoffs. Raw scans can remain an activity signal, but they should not be presented as pipeline or revenue.

Define each metric before the event and keep the denominator visible. For example, meeting conversion should state whether it uses all captures, qualified conversations or target-account contacts. That discipline lets teams compare execution without converting an unverified impression into a financial outcome.

Why the post conference clock lacks a published close time

Technology and Services World starts October 19 and ends October 21, 2026 after 3 full days. The reviewed schedule does not publish the final programme close or expo close, so the two-hour and one-week follow-up timestamps cannot be attached to a defensible clock time yet.

An effective first follow-up confirms the promised action while the conversation is still fresh. Notes move to the correct owner, incomplete fields are resolved and shared material matches the stated problem. Where no commitment was made, a lower-intensity path avoids manufacturing urgency.

Within a week, review target-account coverage, meeting outcomes, unresolved requests and ownership gaps. The exact clock should be anchored to the eventual programme close and internal service levels. Keep a visible exception queue so valuable conversations do not disappear behind a bulk campaign.

Which inputs are missing from a defensible ROI model

The page publishes attendee prices of $3,150, $2,100 and $2,850 for its principal pass combinations. It does not publish booth investment, verified conversation volume, qualified-opportunity value or event-specific conversion inputs, so a cost-per-meeting or return figure would be invented and is omitted.

A defensible return model begins with verified total cost and clearly defined outcomes. Registration prices are known, but sponsorship, space and other exhibitor costs are not established by the reviewed public sources. Conversation volume, qualification, opportunity value and conversion also require actual event results.

Until those inputs exist, report operational evidence rather than a fabricated ROI percentage. Track committed spend, qualified target-account conversations, accepted next steps and influenced opportunities with documented rules. Calculate financial return later from approved CRM and finance data, preserving assumptions and attribution boundaries.