FAQ
Common questions
If something is not covered here, the brief form has a field for it.
Engaging
- How do I start a project?
- Submit a brief at /brief/. Select a discipline, describe the scope, and send it. No discovery call required for Networking and Web. Expect a scoped proposal within 24 hours.
- Do I need to schedule a call before getting a proposal?
- No. A written brief is sufficient. Calls happen when they add value — not as intake theater. If a scoping call is needed after reviewing your brief, that will be requested specifically.
- What happens after I submit a brief?
- A scoped proposal arrives within 24 hours. The proposal documents deliverables, timeline, and compensation before any commitment is made. Nothing is verbal or assumed.
- Do you take on all briefs?
- Not always. If the scope is outside available capacity, outside the verticals served, or would require compromising on quality or ethics, it will be declined — clearly and promptly.
Pricing
- How is pricing structured?
- Project-based, retainer, or hourly depending on engagement type. Public pricing is shown as a starting point only. Every proposal is itemized and indexed to approved scope before work begins.
- Is there a minimum engagement size?
- Typical starting points are: Networking implementation from $3,500, Web builds from $8,500, OSINT due diligence from $4,500, Security assessments from $9,500, and retainers from $1,100/month depending on scope. Final proposals are itemized and indexed.
- Who pays for hardware or third-party costs?
- Hardware is invoiced at cost with no markup. Clients may also procure directly using a provided spec list. Third-party services (hosting, SaaS, licensing) are scoped explicitly — no surprises.
- Do you work with fixed budgets?
- Yes. If budget is constrained, the proposal will scope what is achievable within that budget. Priorities are discussed before scope is locked.
OSINT + Security
- What does "authorization required" mean for OSINT and Security?
- OSINT and Security engagements require, before any work begins: a signed authorization letter specifying the target scope, verification of authority over the target scope, and government-issued identification of the authorizing party.
- Can you test systems I do not own?
- No. Scope is limited strictly to systems and entities the authorizing party has legal authority over. This is not a policy preference — it is a legal requirement. Engagements outside proper authorization will be terminated and, if warranted, reported.
- What is a "pre-engagement brief" for Security or OSINT?
- Submitting a brief for OSINT or Security opens the authorization intake process — not the engagement itself. The authorization steps must be completed before any intelligence or security work begins.
- Can you work under an NDA?
- Yes. Standard NDAs covering the engagement scope are routine. Unusual or overly broad NDA terms may require review before signing.
Delivery + Ownership
- Who owns the work after delivery?
- You do. Full repository transfer, credentials, and documentation are handed over on completion. There are no proprietary systems, no lock-in to ongoing access, and no ongoing license requirements for the core deliverable.
- What documentation is included?
- Every engagement includes documentation sufficient for an independent party to operate, audit, or extend the output. What cannot be documented cannot be verified — documentation is the product, not an afterthought.
- What happens if scope needs to change mid-project?
- Change orders are written and agreed before scope changes. No scope expansion is assumed from verbal conversations. The original scope document remains the binding record until a written amendment is signed.
Technical
- What web stack do you use?
- Primarily Astro for static sites, SvelteKit for interactive applications. Deployments to Netlify, Vercel, or Cloudflare Pages. DNS and edge through Cloudflare. Self-hosted fonts, Plausible analytics — no Google, no tracking pixels.
- Do you work with existing infrastructure or codebases?
- Yes. Audits, migrations, and hardening work on existing systems are common engagements. The brief form covers this under scope and context.
- Do you offer ongoing support after a project ends?
- Maintenance retainers are available. Otherwise, support is available at the advisory hourly rate. The handover documentation is designed to make third-party support straightforward if needed.
- Can you work remotely?
- Most work is performed remotely. On-site work is available for network infrastructure and certain security engagements where physical access is required. Travel and on-site rates are scoped explicitly.
Still have a question?
Start a Brief →