About
Three of us. One team.
Brixel is a small Calgary studio that builds operational systems for small professional firms. Three of us, each bringing a different lens. One point of contact through your engagement; three of us shaping every project. No account managers, no handoffs. Built in weeks, not months.
Who you work with
Three of us. Different lenses, one team.
Engineering, operations, and domain. Each engagement runs through all three lenses at the points where they matter: scoping review before commitment, process and people checks on every deliverable, domain stress-test before the build starts. One of us is your day-to-day contact; the other two shape what gets built.
Engineering
Silvio
Twelve years across business analysis, product ownership, and delivery. Eight as Product Owner on Guidewire InsuranceSuite at Pacifico Seguros (P&C, policy + billing + claims). Brings the technical lens to scoping, the architecture decisions, and the working software at handoff.
- Discovery, requirements, and scoping
- Architecture, code, and delivery
- Working software validated against phase-3 proof criteria
Operations
Diana
Multi-industry process and operations background. Legal owner of the company. Brings the operational lens to scoping, the people-and-process check on every deliverable, and the practitioner read on how systems actually land in real teams.
- Operational design across the engagement
- Process and people patterns surfaced before commitment
- Practitioner read on how the system lands in a real team
Domain
Andrés
Civil engineer. Career inside major construction firms abroad and in Canada. Brings the domain lens to engagements that touch engineering, regulated practice, or on-the-ground operational reality. Stress-tests assumptions before delivery starts.
- Domain and regulatory review
- Stress-test on assumptions before delivery
- On-the-ground reality on engineering and process discipline
Brixel is a small practice based in Calgary. We work with two engagements in flight at once.
How we work together
Four principles, applied every engagement.
One contact end to end.
Whoever you call answers. We do not put a sales layer between you and the work, or a project manager translating between you and the people building the system. One of us is your contact through the engagement; the team is inside every build.
Discovery before design.
Every engagement opens with a Discovery phase, free of charge, written, and evidence-grounded. The stated problem is a hypothesis until the evidence confirms or contradicts it. We do not draw an interface or pick a stack until the actual problem is mapped.
Working software, not slides.
What we deliver runs in production by the end of the engagement. Every methodology artifact (problem map, service architecture, proof system) traces to working software your team uses on Monday morning. We do not build prototypes that sit in staging; we build systems that ship.
Plain language, written down.
Every artifact is written in language a non-technical owner can read. No jargon for jargon's sake. If something needs a technical term, the term gets defined the first time it appears. The deliverables you receive are useful even if you stop working with us; they describe how your firm runs.
Start a conversation
Tell us about your firm.
No template. Write what is on your mind. A real person reads everything that lands here and replies within 24 hours.
Reply inside 24 hours