For emergencies, call 911.Lucas + Sentinel · Detailr Corp

Meet the team

The people building Lucas and Sentinel.

Jacob leads product and business direction. Trey leads technical development. Together, they work on the exchange between residents and participating departments.

Jacob Brink — product and business direction

Jacob Brink is Chief Executive Officer of Detailr Corp, the company developing Lucas and Sentinel. His work connects the problems residents and departments face with the priorities behind the applications. He reviews the user journeys, defines product requirements and coordinates the business decisions around the work.

For an agency considering Sentinel, that means discussing the operating questions as well as the proposed feature. Who would publish a request? What would a resident need to understand? Who would review information that comes back? Those questions help define an evaluation that is specific enough to be useful.

Jacob is also known as Jacob Dawson Brink. His existing profile connects both names and explains his current responsibilities and relevant operating experience.

Source: Read Jacob Brink’s profile

Trey Everett Hugan — technical development

Trey Everett Hugan is the technical co-founder and Chief Technology Officer of Detailr Corp. He works on the applications and the technical decisions that connect their workflows. The resident and department experiences need to fit together without treating their users or responsibilities as interchangeable.

A resident may see a simple action, such as opening a department update or choosing what information to submit. The department needs a usable way to review that information and handle the next step. Trey’s role connects those requirements with the application work behind the experience.

Technical development also involves examining how a proposed change affects the rest of the workflow. A new input, permission or status needs an understandable purpose for the person using it. The team’s public explanation should remain aligned with the current product.

Source: Read Trey Everett Hugan’s profile

Where their responsibilities meet

Product direction and technical development come together in the sequence of a task. A request needs a recognizable source and a clear audience. A resident needs enough context to decide whether an observation is relevant. Department staff need to understand where the response goes and who handles it.

In a fictional evaluation, an agency could ask the team to follow a request from publication through review and assignment. Jacob can discuss the intended use and operating questions; Trey can discuss how the current application supports the steps. The agency can then identify what it needs demonstrated or clarified before deciding whether the product fits.

That exercise describes an evaluation approach, not an agency deployment or an investigative result. The useful outcome is a concrete set of questions, observed behavior and next steps.

Source: Use the department evaluation guide

A shared company, distinct responsibilities

Lucas and Sentinel are developed within Detailr Corp. Lucas is the resident experience; Sentinel is the department workspace. The founding team’s product and technical roles do not replace a department’s responsibility for the information it publishes or the review process it operates.

Residents should be able to distinguish a product provider from an issuing agency. Departments should be able to distinguish the software workflow from their own approval, staffing and emergency-communication duties. The team’s role is to explain the offering clearly enough for those questions to be examined.

Source: About Detailr Corp · How Lucas and Sentinel fit together

Bring a specific workflow to the conversation

A useful introduction can start with one task your department wants to evaluate: an area-specific request, the review of incoming information or a staff handoff. Explain the current process, who is involved and what a successful demonstration would need to show. The team can discuss the current product against those requirements.

The business inquiry channel is for product and company questions. It is not a place to submit emergency reports, private evidence or sensitive resident information. For an emergency, call 911; use your local agency’s official channels for reporting and warning guidance.

Source: Discuss an agency evaluation · Explore the company’s history

Your next step

A clearer way to stay informed and contribute.