FutureCon Events runs cybersecurity conferences across North America. Behind each event is a connected set of jobs: managing contacts, registering attendees, coordinating sponsors, communicating with participants, recording attendance and supporting continuing professional education.
The FutureCon Omni App brings these operational workflows into a custom application. The project's single senior developer provides continuity, working closely with the people who use the system. Weekly team conversations, written feedback and a shared ticket process turn day-to-day needs into a continuing programme of practical improvements.
What the work makes possible
See the people behind the numbers.
Attendance summaries link to the underlying registrations, so the team can inspect and export the records behind each count.
Keeping feedback connected to delivery
FutureCon's team brings specific examples from its work into the development process. A request might concern how to find a sponsor, which records belong in an outreach list, or what information someone needs before merging duplicate contacts. Those examples give development a clear operational purpose.
As the application grew, the process for managing requests grew with it. A Tickets app introduced in September 2026 gave the team a shared place to record requests that had previously arrived through separate emails. Tickets include urgency, ownership, discussion and status. Completed work remains searchable, and a ticket raised from a page can preserve the view and filters that prompted the request.
Release updates connect changes back to those requests. They explain what changed and how to try it, giving the team a concrete starting point for its next review.
Making database cleanup easier to judge
Maintaining useful contact data requires more than detecting possible duplicates. Someone still needs to decide which information is current and which record should remain the main record.
Omni's cleanup workflow supports that decision with side-by-side record comparisons. The team can review differences in contact details and event information before choosing what to keep. An October refinement added the date each record was added and its latest associated event, giving users more context during duplicate review.
The same attention to data handling appears in marketing lists. Lists refer to contacts without making list membership and contact identity the same thing. Import previews identify existing contacts and show proposed changes for review. These features support ongoing database maintenance while keeping the team's decisions visible.
Connecting everyday event tasks
For sponsor coordination, search was extended to find a sponsor by name and show the events associated with that sponsor. The team can move from a company to its event history without starting a separate search for every event.
For continuing professional education, a new CPE record can be populated from an event registration. The person's name and email carry across, and the workflow checks for an existing CPE record for the same person and event. This removes retyping from that step and helps avoid duplicate entries.
Outreach also uses information already in the system. The team can find people from earlier events who have not registered for an upcoming event, refine the group and use it for a marketing list. Additional filters allow staff to narrow that selection according to registration and attendance information. Campaign testing and duplication make it easier to review an email and reuse an existing campaign as a new draft.
Turning a reporting question into a reusable feature
Attendance reporting illustrates how the project moves from a business question to a repeatable tool.
The team wanted to compare confirmations with actual attendance: who confirmed and came, who confirmed but did not come, and who attended without confirming. The senior developer first examined individual events, then developed an Attendance view so the same questions could be explored across events with imported final attendance lists.
The view links summary figures to the underlying registration records. Staff can inspect the people behind a count and export the resulting list. This gives the team a practical basis for discussing attendance patterns and event planning, with the supporting records close at hand.
A short and visible improvement cycle
The October delivery cycle provides a concrete example of the working relationship. On October 8, the team requested campaign testing and duplication, additional contact types, more selective past-attendee lists and attendance analytics. The October 12-13 release included those capabilities alongside ticket-driven improvements to sponsor search and CPE entry.
The next feedback continued the cycle. FutureCon's operations team confirmed that the sponsor-search and CPE changes matched its requests, while asking for a more specific in-person attendance breakdown. The response provided both evidence that particular changes were useful and a clear next refinement.
An ongoing delivery partnership
The result is an operational application supported by a repeatable way of improving it. FutureCon contributes the working context, Redwoods Consulting provides the client engagement, and the senior developer brings senior development continuity through 1WAYTO. Together, the process keeps feature development, database maintenance and user feedback connected as the team's needs evolve.