The question was ordinary enough to be devastating. A large education customer in Texas wanted to know why technicians arriving to service its security system were asking the customer where certain cameras were. Christopher Hugman was running operations for the integrator. He understood the reason, and it was not flattering: there was no current digital map that carried the system’s memory. The equipment had a place in the building. The knowledge about it had places everywhere else.
Some of it lived on marked-up floor plans. Some sat inside spreadsheets. Photos waited on individual phones. A PDF crossed an inbox and immediately began aging. The next person in the chain received a thinner version of the truth than the person before. By the time a technician returned months or years later, an installed camera could be easier to spot on the ceiling than in the company record.
Hugman had spent decades around networks and physical-security projects. He knew the choreography too well to blame a careless employee. This was how an industry had learned to work. A site survey began as a walk through a real building, full of conversation, angles, obstacles and decisions. Then the richness was squeezed into paper, static files and memory. The ritual was familiar. Its cost hid inside revisions, repeat visits, delayed proposals and awkward questions.
That old line from his telecommunications days became an unusually good description of the opening. The physical-security business was spending plenty of time doing work over. Hugman and software veteran Maureen Carlson co-founded System Surveyor in Austin in 2014. The product they launched the following year put a floor plan on a tablet and made it behave less like an attachment and more like a conversation.
A site walk is where the project learns what is true
Walk into a school, hospital, office or warehouse and the abstract project becomes physical. A camera needs a particular view. A door has hardware, power and access rules. A cable route meets a wall that the proposal did not anticipate. The customer points to a corner and explains what happens there at 6 p.m. This is precious information because it arrives early, when decisions are still cheap to change.
Hugman’s product insight was to capture that context where it appeared. A user could import a floor plan or map, drag devices into position, attach photographs and requirements, draw coverage areas and begin a bill of materials. The visual record could then be shared with a customer, colleague, subcontractor or manufacturer. Instead of waiting for a polished proposal to discover a disagreement, people could point at the same plan while the design remained pliable.
The floor plan is a clever interface because it does not ask a security professional to think like a database administrator. People already orient themselves visually inside buildings. A symbol placed at the northeast entrance can carry model, quantity, photographs, notes and status without losing its central meaning: this device belongs here. The visual does not replace the data. It gives the data an address.
There is also a social trick inside the design. A customer who struggles to parse a long scope document can react to a coverage cone on a map. An installer can see the decision sales made. A future service technician can find the installed asset without asking the customer to become the archive. Collaboration, in Hugman’s telling, is not an inspirational poster. It is everyone having access to the same useful picture.
An engineer accumulates scar tissue
Hugman’s route to software was pleasingly indirect. He earned a bachelor’s degree in electrical engineering from Southern Methodist University in 1985, then returned for an MBA, completed in 1991. His early career moved through telecommunications at Southwestern Bell and Wiltel, followed by network-building work at Brooks Fiber Communications. By 1999 he was senior vice president of engineering at ConnectSouth, then vice president of operations at Security Broadband.
Telecom gave him large systems, regulation and networks. Operations gave him consequences. In 2002 he became president of Safe Sight, an Austin security and loss-prevention technology business. Seven years later the company joined Knight Security Systems, where Hugman led Central Texas operations and later worked on service innovation. He had moved from designing networks to running the organizations that promised customers those networks would perform.
This is the useful kind of founder-market fit: not merely a résumé that matches a sales deck, but an ability to feel where a workflow pinches because you have limped through it yourself. Hugman knew the difference between a design that looked complete in the office and one that survived contact with a building. He knew how missing context appeared later as labor, apology and margin erosion.
Expertise works better when it keeps listening
Domain experience can make a founder decisive. It can also make one deaf. Hugman’s public comments reveal a useful counterweight. He talks often about a “mutual success mindset” and credits the user community with shaping the product. When System Surveyor began building its second generation in 2022, the team shared concepts and beta versions, then prioritized the changes it believed would help the broadest set of users.
The resulting System Surveyor 2.0 expanded native tablet support from iPad to Android, rebuilt the interface, improved cloud syncing and strengthened drawing and annotation. The web editor followed with a matching experience. These changes sound like product-release furniture until one imagines the user: standing in a basement with unreliable connectivity, trying to mark a cable route while a customer explains three other constraints. Offline usefulness and familiar controls are not garnish there. They are the product.
The bars above are an editorial illustration, not survey data. Their point is the fragmentation Hugman describes: each medium is useful, but none naturally becomes the current shared record. System Surveyor’s wager is that the project should not have to choose between a visual plan and structured information. It should keep both, together, and update them as the work changes.
That sentence is Hugman’s advice to people entering security. It also describes a product-management discipline. Curiosity notices the workaround. Humility accepts that the field technician may understand the edge case better than the founder. Questions turn a complaint into an observable workflow. The engineer still has to choose, simplify and ship, but expertise becomes a sharper listening instrument rather than a reason to stop listening.
Make the record survive the ribbon cutting
Many project tools lose relevance when installation ends. Hugman’s aspiration extends beyond the proposal and handoff. He has described an always-current visual record that remains useful through maintenance and replacement. This matters because a physical-security system is not a single purchase. Cameras age. Doors change purpose. Firmware, networks and policies evolve. The building develops a history, and every unrecorded change makes the next decision more expensive.
In May 2026, System Surveyor launched a native phone app aimed at project managers, technicians and subcontractors. The move puts surveys, floor plans, photos and status updates onto the device already in a field worker’s pocket. It also closes a loop in the original story. The technician who once arrived without the project’s memory can now carry that memory to the device, update it, and send the richer record back.
Hugman remains measured about the industry’s fashionable subjects. On artificial intelligence, he has acknowledged real innovation and plenty of noise, emphasizing education and practical adoption. His operating instinct favors tools that survive the work. A prediction is interesting. A correct floor plan at the moment somebody needs it is useful.
Watch: Hugman on helping integrators deliver on technology’s promise
The founder’s story is therefore less about replacing a clipboard than preserving truth as work changes hands. Sales sees one part of a project. Design sees another. Installation discovers what neither could know. Service inherits all of it, usually with the fewest witnesses left in the room. A living visual record lets each group add to the same account.
There is an almost comic modesty to the floor plan. It is a bureaucratic rectangle, a document found behind office doors and next to fire extinguishers. Hugman saw that it could become a shared language. Put the devices where they belong. Attach what people know. Invite the customer to look. Keep the record after everyone goes home.
The awkward question from that education customer did more than expose missing camera locations. It revealed a company repeatedly paying to rediscover something it had once known. Hugman’s answer was software, but the more transferable idea is a question for any operator: where does your organization keep losing context at the seams? Somewhere in that small embarrassment, a useful product may already be waiting.