One founder.
Many hats.

PetroFeed combined locations, companies, equipment and changing operational information. That experience helped draw him toward atomic composition and the shared foundation behind 8DB’s modalities. His contribution is architectural direction and insistence on coherent behavior across the pieces.

Connected information · Model composition · Engine direction

PetroFeed put industry information on a mobile map. Later work with SmartGrid and TELUS brought physical spaces, sensing and software into the same picture. Those experiences inform the questions he brings to native mesh: how useful context travels between environments, and how control travels with it.

Field workflows · Mobile context · Physical/digital systems

His early work on economic evaluation connected technical choices with real operating decisions. At 8Braid, he has pushed performance comparisons beyond speed to storage, resource use, security and combined workloads. This hat keeps asking what was measured, against what, and what the result means for a customer.

Economic consequences · Workload framing · Evidence discipline

LifeSocket explored participation and communication through relationships between people and places. At 8Braid, Ashley made native encryption, post-quantum protection and cryptographic evolution design priorities. He owns that product intent while recognizing the distinct role of specialist engineering and independent security review.

Privacy by design · Access boundaries · Cryptographic lifecycle priorities

PetroFeed’s mobile application made an industry’s activity accessible through a map. In August 2014, contemporary coverage reported it as Canada’s most-downloaded business app earlier that week. That experience informs his direction for the 8DB App: bring the underlying capability into a useful, understandable workflow.

Mobile product leadership · Connected workflows · App direction

PetroQuick began as a tool for a real operating need. His later products explored industry information, community participation and physical spaces. At 8Braid, he brings that range to the distinction between an Engine developers can build with and an App people can use directly.

Customer problems · Workflow design · Product iteration

Selling PetroQuick brought him into direct contact with the people making operating decisions. Building subsequent products exposed the work required to connect separate systems. At 8Braid, he carries that perspective into examples, modality references and the complete path from input to usable value.

Customer context · Integration perspective · Technical explanation

His public interviews have connected networked information with practical industry needs. At 8Braid, he shapes the website and Journal around that same task: explain a different approach, preserve the competitive context and make the useful distinction easy to see.

Positioning · Industry context · Founder-led communication

PetroQuick gave him early experience selling software to industry decision makers. PetroFeed added company building and fundraising; 2014 coverage reported $3.1 million in seed financing. At 8Braid, the job is to find the workloads and relationships where the technology can earn a place.

Software sales · Fundraising experience · Industry relationships

His grounding in the family oil and gas business led to economic evaluation software and then PetroQuick. Building later ventures added the founder’s responsibility for allocating scarce time and capital. At 8Braid, this hat owns business planning and brings in qualified accounting and legal support where needed.

Operating economics · Resource allocation · Founder accountability

PetroFeed involved building a team around a new product. His professional account of the TELUS work describes assembling a team around a combined software and hardware program. The next chapter calls for people who bring complementary judgment, challenge assumptions and carry work through to something others can use.

Team formation · Complementary strengths · Founding-team direction