Somewhere around February, you sit down for a software demo while registration questions are arriving, hiring paperwork is unfinished and somebody needs the latest version of the health form. The salesperson shares a polished screen. A camper profile appears. The cursor moves cleanly from tab to tab. Nothing is misspelled, nobody has entered the same parent twice, and the Wi-Fi never drops.
You can watch that presentation and learn almost nothing.
A useful demo is closer to a fire drill. You supply the situation, the vendor works inside the product, and every awkward pause becomes information. The goal is not to see what the software contains. It is to see what the software makes your staff do when camp is full, the office is loud and a parent is waiting on the phone.
Bring your own camper
Vendor sample accounts are built for demonstration. The household is tidy. Forms are complete. Balances make sense. Every person has a distinct email address.
Your database will not look like that.
Before the meeting, write a fictional household that resembles the records your office actually handles. Give the campers different sessions. Add separated parents with different permissions. Include a grandparent who pays but should not receive health information. Leave a required form unfinished. Put money on the account, then change something that affects the balance.
Ask the salesperson to create that household from scratch while sharing the screen. Do not accept a tour of a household prepared earlier. You need to see where relationships are defined, how permissions are assigned and what happens when the family structure does not fit the default path.
Then change the facts. Move a camper to another session. Add an authorized pickup person. Correct the primary email address. Mark a form incomplete after it was previously accepted.
That is where the product starts telling the truth.
Narration is not execution
A weak demo relies on sentences that begin with “you can.” You can export that. You can customize this. You can give staff access. The feature may exist, but the explanation conceals the steps, permissions and cleanup attached to it.
Ask to see the action completed.
If the vendor says reports can be customized, request a report using fields you chose. If staff permissions can be restricted, ask the presenter to create a role and show what that user sees. If an email can be sent to families with missing forms, have the presenter build the recipient group and display the message preview.
Stay quiet while the work happens. A salesperson filling silence with commentary can make a long workflow feel shorter than it is. Watch the cursor instead.
Also notice when the presenter leaves the main application. A spreadsheet, separate document editor or support portal may be a sensible part of the process. It is still part of the process, and your staff will have to use it.
Ask August questions
A demo usually takes place in a quiet room during the buying season. Your consequential software use happens when campers are on property.
Put the presenter inside that day.
Say a counselor brings a camper to the health center, but the nurse cannot find the latest medication instructions. Ask how the nurse locates the record and how the system shows who last changed it. Say a parent calls the office to change an authorized pickup person while the camper is already assigned to an activity. Ask where the change appears and which staff members are notified.
Then test the handoffs. Registration data may need to reach transportation, food service, cabin assignment or the health center. The relevant question is not whether the data exists. It is how the right person receives the current version without rebuilding a list.
Use situations with interruption built in:
- A staff member begins a task, gets pulled away and returns later.
- A family submits a correction after an internal report has been created.
- Two employees edit the same record.
- A seasonal user opens the wrong camper profile.
- Internet access becomes unreliable at a field location.
- A parent calls from a different email address than the one on file.
- A form is complete, but the answer requires staff follow-up.
Ask what the software records, what it warns about and what it permits. Those are different things.
The clicks that count
Counting clicks alone is crude. A short workflow can still be confusing, and a longer one may contain sensible checks. What matters is the amount of judgment your employee must supply between clicks.
Watch for screens where the user has to remember an internal code, know which similarly named report to select or understand a status label that is not explained on the page. Those demands become training obligations. They also become support requests when seasonal staff arrive.
A useful demo table looks like this:
| Demo test | What to watch |
|---|---|
| Correct a family relationship | Whether the change updates connected records or requires separate edits |
| Move a camper between sessions | How capacity, billing, forms and assignments respond |
| Find an incomplete health item | Whether staff can see the missing information without opening each record |
| Restrict a seasonal staff account | What the employee can view, change, download and send |
| Reverse a payment entry | How the correction appears in the family account and internal history |
| Export an operational list | Which fields are available and how current the export remains |
| Record a parent communication | Where the note lives and which users can see it |
| Resume interrupted work | Whether drafts, filters and unsaved changes remain available |
Do not rescue the presenter by simplifying your request. If the workflow depends on a setting that is not enabled in the demo account, ask the vendor to explain who enables it, how long that setup takes and whether it belongs to ordinary configuration or paid services.
The distinction matters at contracting time. A checkbox already available to your administrator is different from a customization request, even if both produce the same screenshot.
Dazzle has a proper place
A clean dashboard is pleasant. Automated messages can be useful. A colorful mobile view may make the presentation feel current. None of those screens deserves extra weight simply because it demonstrates well.
Presentation-friendly features tend to be visible and self-contained. Camp operations depend on less photogenic work: correcting records, controlling access, tracing changes and recovering from mistakes. Those tasks rarely produce the moment in a demo when everyone nods.
Artificial intelligence features demonstrate especially well, which is why they deserve their own test. The section below sets one out.
Be equally cautious with phrases such as “fully integrated.” Ask which system holds the original record, how often information moves, what happens after a failed transfer and where staff see the failure. Integration is a chain of ownership. The demo should show the links.
Test the AI feature, not the announcement
“AI-powered” is a label, not a specification. On a vendor website it can mean the software drafts an email, summarizes notes, classifies an incoming message, searches records in ordinary language, recommends an action, identifies a pattern or triggers an existing automation. Those functions do different work and carry different risks. A draft can be reviewed before it leaves the office. A summary can omit the sentence that changes a transportation decision. A recommendation can look authoritative without showing which records produced it. An automation can send something before a person sees it.
Start by replacing the label with a plain verb. The feature drafts. It searches. It summarizes. It predicts. It routes. If the vendor cannot finish that sentence precisely, the website is carrying more weight than the product. Two companies in Camp Management Software may both advertise an assistant while one produces editable text and the other retrieves information from camper records.
Then give it a real day. A generic prompt about writing a cheerful parent email proves a text generator can write a cheerful parent email. Ask instead for a message about a bussing change when siblings attend different weeks. Ask it to summarize a parent thread containing an extended-care adjustment and a pickup authorization buried in an earlier reply. Ask it to find the difference between a camper's registration record and the note added after drop-off. Then interrupt it: change the pickup plan, remove access to a record, add a part-time staff member who should see only that afternoon's information.
| Website claim | What to ask the vendor to show | Pressure test |
|---|---|---|
| AI writing | The source material, editable output and approval step | Draft a parent message without inventing program details or pickup instructions |
| Smart summaries | Which records are included, excluded or prioritized | Summarize a thread containing a late extended-care change |
| Natural-language search | The systems and fields the search can access | Find the current transportation note when older notes conflict |
| Intelligent recommendations | The basis for the recommendation and the person responsible for acting | Explain how weekly enrollment and part-time attendance affect the suggestion |
| Automated communication | The trigger, recipient rules and stop controls | Prevent a message from reaching a family after the underlying plan changes |
| Pattern detection | The data used and the treatment of missing or inconsistent records | Separate a real attendance pattern from a canceled program day |
Inclusion is not an endorsement. These are claim types, not vendor assessments.
The distinction between drafting and deciding matters most. Software that drafts a reply gives your staff something to inspect. Software that decides who receives the reply, which record governs or what action follows has moved deeper into operations.
Ask where the AI answer came from
An output can look finished while concealing an unfinished data problem. Your registration system may hold one address, the transportation list another and an email thread a later correction. The software has to choose what to read, and you need to know how.
Ask the vendor to show the source behind an answer. If a summary says a camper is approved for pickup by a particular adult, the interface should let the staff member reach the underlying record rather than trust the sentence on screen. Ask about freshness: when newly entered information becomes available to the feature, what happens during a sync delay and whether the screen shows when its source was last updated.
Permissions belong in the same conversation. An assistant should not become a side door around role restrictions by summarizing information the user could not otherwise open. Do not accept “it follows your permissions” as the demonstration. Log in under the actual roles.
Then read the paperwork. A feature may be included in your plan, sold as an add-on, restricted by usage, enabled automatically or available only after new terms are accepted. Ask what activates it, who at camp has authority to activate it, whether it can be disabled for the organization or only per user, and what happens to prompts, drafts, uploaded documents and generated answers after a user deletes them. “Your data is secure” does not say whether information is retained, reviewed, shared with another provider or used to improve a model. Those are separate questions, and the answers belong in the contract. Ownership matters here too, because the party processing the prompt may not be the brand on your invoice — CampBuzz has documented who owns your camp software now.
Finally, notice that the easiest AI tool to approve is usually the one that appears harmless. A writing assistant lands in the communications screen, staff discover it saves keystrokes, and parent messages start being drafted from camper information without a shared rule for review. That is a management change even if procurement never called it one. Decide which uses require human approval before the feature opens to summer staff, and keep accountability visible: the employee who approves a generated message owns the communication.
Make permissions visible
Software access is often demonstrated from an administrator account because that account can reach every screen. Most employees will not use that view.
Ask the presenter to switch roles during the meeting. A health center employee should not be represented by a narrated description of health center access. You need to see the actual menu, search results, exports and camper record available to that role.
Test subtraction, not only addition. Remove permission after a seasonal employee has already downloaded a report. Ask what remains in the system history. Disable the account. Ask how an administrator reviews active users and identifies accounts that should no longer exist.
The product’s permission model may fit the way authority works at your camp, or it may force broad access because narrow roles are difficult to maintain. You cannot see that from the administrator dashboard.
Support belongs inside the product test
When the presenter encounters a problem, do not let the moment disappear. Ask how your employee would get help with the same issue during camp.
Have the vendor show the support path rather than naming it. Where does the user submit a request? What account information is attached automatically? Can the employee include a screenshot? Where can an administrator see previous requests? If support access varies by contract or season, ask for that language in writing.
Training deserves the same treatment. A library of videos is not the same as task-level guidance available while an employee is stuck. Ask the presenter to find the instruction for the exact workflow that caused trouble in the demo.
A support promise sounds generous in a sales conversation. A support process is something you can inspect.
End with the failed task
Before the meeting ends, return to the moment that went poorly. It may be the household permission change, the session move or the report that required an export and manual cleanup.
Ask the presenter to perform it again using the recommended method. Then request written confirmation of any configuration, service or contract condition required to make that method available in your account.
A polished demo shows how software behaves when everything has been prepared for it. Your job is to remove that preparation and put August on the screen.
Author
Maggie HollowayEditorial byline, CampBuzz
Maggie Holloway covers buyer guides and industry reporting for CampBuzz: the questions worth asking, the fine print worth reading, and the ownership changes worth knowing about before you sign. CampBuzz does not rank vendors.