Frequently Asked Questions

Your Blueprint is a technical architecture document: the architectural system design, API contracts, data model specifications, and a strategic implementation plan — delivered as a static, async document your team or your AI agents can build from. It guides the strategy; your team keeps full control of execution.

The format follows your need — from a quick technology read to the full Blueprint with specs your AI agents can execute. What never changes: you receive written documents, with reasoning and trade-offs, verified by a senior expert and measured against acceptance criteria agreed with you.

Because nothing reaches you as AI-only work. Every comparison and piece of research is reviewed by a senior expert before delivery, and every deliverable is measured against acceptance criteria agreed with you. More on the profile that signs off on every document in Backed by Expertise, Not Just AI Output.

No — by design. HELMQ works on the strategy and planning side: we compare technologies and costs, define which profiles you need, and deliver the blueprints so your team — or your AI agents — can build with certainty. That planning weight stops falling on their desk, or on yours.

Perfect — that's the ideal case. We work alongside your team and your technical leadership, never in place of them. The blueprint is designed to be handed off to any dev team or AI agent, with everything they need to build without guessing your intent.

Every deliverable includes revision rounds agreed up front: the Diagnostic gets 1 round within 7 days; the Decision Blueprint, 1 round within 10 days; the Pilot Blueprint, 2 rounds within 14 days. The Architecture Co-Pilot's revisions are continuous and defined in your contract. Scope is agreed in writing, and we hold ourselves to it — if a deliverable doesn't meet that scope, we fix it or refund.

Diagnostic: 72 hours. Decision Blueprint: 5 business days. Pilot Blueprint: 15 business days. The Architecture Co-Pilot is monthly and continuous. The clock starts once payment clears and we have what we need to begin.

Yes. Every engagement is covered by a mutual NDA. Your ideas and business logic are protected from day one.

Once the mutual NDA is signed, we ask for context: your goals, the budget you plan to invest, the team you can count on, and whether you'll build it yourself or with AI agents. You answer however you prefer — voice notes, videos, messages or files. The more you share, the more precise your deliverables.

Yes, when the engagement calls for it. We help you define the roles the plan requires, screen candidates, and run technical interviews — so whoever builds it can actually execute what's in the document. Agreed in writing as part of scope up front, or as a separate engagement.

More than the plan would have. Systems built without headroom get expensive exactly when you can least afford the disruption — the fix arrives as an emergency instead of a line item. We review what you have today and tell you, in writing, what needs to change and when, before growth forces the decision.

We design the full solution. Not just 'here's what's wrong' — we deliver 'here's exactly how to fix it and build it right.' Learn more about technical due diligence →

Any business running on software that matters to its operation — ERP, e-commerce, CRM, internal tools, or a product you're building from scratch. We recommend based on your business constraints, team, and growth trajectory, not on what's trending.

Yes, for the Pilot Blueprint and the Architecture Co-Pilot. Both are invoiced, and you may pay by bank transfer or by card, whichever your finance team prefers. The Diagnostic and the Decision Blueprint are card only, so you can purchase them without a call. Work begins when the invoice is settled or the payment clears, and the delivery date is counted from that point.

We tell you before we do it. Scope is written down before work starts, so it is always clear which side of the line a request falls on. If it is inside scope, it is included. If it is outside, we send you a change order with a fixed price and a date, or we recommend a different engagement that fits it better — and nothing proceeds until you approve. You will never receive a bill for work you did not agree to.

Because hourly billing pays us for the time a problem takes rather than for solving it, and it puts you and us on opposite sides of every estimate. A fixed price for a fixed document removes that. You know the cost before you commit, your finance team approves one number, and the incentive to be thorough and fast points in the same direction for both of us. It also means the deliverable — not our calendar — is the thing you are buying.

No, and never. We take no commissions, rebates or incentives from any vendor, and we resell nothing. Money reaches HELMQ from one direction only: the company that hired us. The single fee we ever pay out goes to the person who introduced us, it is calculated on our own fee, and it is paid regardless of what the document recommends. That term is written into the referral agreement before any introduction is made. Read the full policy in How We Stay Independent.

No — by design. We deliver the blueprint; your team or your vendor executes it. Two reasons. First, independence: if we profited from the build, our recommendation on how large that build should be would be worth less. Second, it is what makes an independent technical review of your vendor's work credible — we have nothing to win by finding a bigger project. The Pilot Blueprint includes a step-by-step build playbook precisely so that whoever executes it does not have to interpret our intent.