How We Work
Flexible engagement, clear outcomes
We adapt to your team size, timeline, and technical complexity. Most clients start with a focused scope, then expand into longer-term support only when it creates real value.
Engagement Models
Choose the right level of involvement
Short, focused technical assessments (1-4 weeks). Security and technical debt reviews. Roadmap creation with clear milestones.
Lead specific initiatives alongside your team (1-6 months). Coordinate vendors and internal engineers. Weekly progress reviews and demos.
Execute agreed designs with your engineers, or manage trusted contractors under our supervision. Full documentation and handover.
After project delivery: warranty, maintenance retainer, or long-term engineering support for releases, observability, security, and sustaining work.
Typical engagement timeline
Week 1: Discovery
A focused call to understand your system, team, and the problem you need solved. We map out risks and what success looks like.
Week 2: Proposal
A written proposal with scope, risks, milestones, and a clear definition of done. No surprises later.
Week 3+: Execution
Work begins. Bi-weekly demos so you always know where things stand. Scope can flex as we learn more.
Final: Documentation & Handover
Full documentation, knowledge transfer sessions, and a clean handover. Your team can own it from day one.
Optional: Ongoing Support
Bug-fix window, maintenance retainer, or long-term engineering support for security, release pipelines, log triage, and sustaining work.
Pricing
Commercials and pricing
Transparent engagement formats — scoped separately from delivery
Pricing depends primarily on complexity and risk (security/kernel work is harder), timeline urgency, and whether on-site access is required (remote is default).
Common starting scopes are a 1-week discovery, a bring-up / unblock sprint, or a release engineering assessment. Defined scope comes first; broader engagement comes later only if it creates value.
Recurring work is usually anchored to a specific responsibility: embedded LTS, fleet log triage, scanner integration and security gates, Yocto CVE review, release engineering, or fractional technical leadership.
To get a fast estimate, send: your goal, current stack + hardware platform, whether you need project delivery or recurring support, and any deadlines. We’ll respond within 24 hours with a rough range or clarifying questions.
Project-based delivery
Defined scope, deliverables, milestones. Fixed or milestone-based billing.
Technical retainer
Monthly advisory + focused engineering. Predictable cost, flexible scope.
Long-term engineering support
Ongoing recurring ownership for sustaining engineering, observability, security hardening, release engineering, or licensing operations — runs as long as the client has ongoing need.
Warranty & maintenance
Post-delivery bug-fix coverage, maintenance retainer, or SLA-based escalation support — priced separately from delivery.
Ready to start?
Most engagements begin with a 1-week discovery. Tell us about your system and we'll take it from there.