How We Work
How Desktop Leafpoint runs programming consulting for embedded software delivery — from briefing through handoff with firmware teams.
Programming consulting for embedded work fails when it is treated like a generic IT project. Desktop Leafpoint runs engagements in four stages so your lab, your repo, and your release date stay aligned. Use this page to see the rhythm before you browse engagements or request a briefing.
Briefing
We map your board family, toolchain, release train, and who owns drivers versus application firmware. You leave with a written scope sketch — not a vague proposal deck.
Lab alignment
Access to repos, CI, and hardware-in-the-loop is confirmed. If we work on-site in Hat Yai or at your lab, we agree bench time and contact points for peripherals that only exist on the prototype.
Delivery cadence
Weekly checkpoints tied to binaries and test logs. Advisory retainers use a standing review slot; delivery partnerships join your stand-ups and own named milestones.
Handoff
Notes land in your wiki: known hazards, flash map decisions, and the open questions still owned by your team. Engagements end on a clear date — we do not linger without a new brief.