Delivery Process
How It Works
A proposal-stage information path with written scope boundaries.
Choose Service
Explore service context and identify a non-sensitive objective for discussion.
What we do
- Review service context and any informational price
- Email non-sensitive background for proposal-stage discussion
- A later written proposal determines any availability
What we need from you
- Nothing at this stage — browse and decide at your own pace
Email discussion only
No public contact form, payment, intake, checkout, or work-start authority is enabled for this market.
What we do
- General inquiries: [email protected]
- Privacy matters: [email protected]
- Do not send credentials, payment-card data, government identifiers, or sensitive-category data
- No inquiry creates a contract or service commitment
What we need from you
- Completed intake form after payment confirmation
- Service-specific documentation, credentials, or materials
- Requirements confirmed within the intake form for your service
Separate written decision, if applicable
A later written proposal controls any scope, entity, timing, price, currency, payment, intake, delivery, and terms.
What we do
- No work starts from browsing or email alone
- Regular progress updates via email
- Deliverables provided according to confirmed scope
- Timeline confirmed during intake based on scope
- Delivery schedule reflects complexity and requirements
What we need from you
- Timely responses to clarifying questions (within one business day)
- Final content assets at agreed milestones (app projects)
Handoff & Support
Review all deliverables, request scope-aligned revisions, and receive handoff documentation.
What we do
- Handoff session to review all deliverables
- Revision period for scope-aligned adjustments
- Documentation and next-steps guidance
- Optional scheduled advisory guidance via Monthly Security Advisory under separate scope
What we need from you
- Review and feedback within the included revision period
- Written confirmation of scope-aligned revisions
BilgeQor Method
The Security File turns risk signals into decisions.
Official market data shows where risk exists. The BilgeQor Security File connects that context to your real websites, apps, accounts, payment flows and team responsibilities, so leaders can decide what to fix first.
What the Security File contains
A Security File is not a generic report. It is a structured decision record for the assets, workflows and risks covered by the agreed scope.
01
Market and sector context
We connect official market signals and industry exposure to the business surfaces in scope.
02
Exposure map
We map websites, apps, accounts, payment journeys, admin roles, vendors and customer-facing workflows.
03
Priority register
We separate urgent risks, important improvements and lower-priority findings so the next action is clear.
04
Executive summary
We provide a concise summary that leadership, operations, vendors or insurers can read without needing raw technical detail.
05
Remediation roadmap
We turn findings into a 14 / 30 / 90-day action path with ownership, evidence notes and follow-through guidance.
Why this matters
The file gives your team one place to understand what was reviewed, what matters, what changed, and what still needs a decision.
What it is not
- Not a guarantee of perfect security.
- Not a certification or compliance verdict.
- Not a per-company loss estimate or fear-based claim.
What you receive at handoff
Security Reviews
- Written security review report (PDF)
- Prioritised finding register with remediation order
- Executive summary suitable for board or insurer presentation
- Remediation guidance notes per finding
- Coverage summary per package scope
- Post-remediation confirmation result (hardening services)
App & Product Services
- Agreed deliverables per intake confirmation
- Source code repository access (where applicable)
- Build artifacts and deployment documentation
- App store submission support documentation (where applicable)
- Handoff session with written notes provided
Advisory Services
- Monthly advisory brief
- Quarterly posture summary
- Prioritised action list per review cycle
- Direct advisory channel access within agreed scope
How Scope is Protected
Clear scope boundaries protect both sides. Inquiries and engagements are handled with a confidentiality-first workflow. You know what is included before work begins, and what intake confirms is what gets delivered — under senior-led review with documented outputs.
Intake Defines Scope
Before work begins, the intake form captures your specific requirements. Deliverables are confirmed in writing.
Timeline Confirmed Post-Intake
We do not commit to timelines before understanding your scope. Delivery schedule is confirmed after intake review.
Add-On Pricing Visible Upfront
If scope expands mid-project, add-on pricing is already known. No negotiation friction.
Custom Scope via Discovery Call
Prevents under-scoped purchases. A discovery call qualifies requirements and scopes the project accurately.
Progress updates
Via email at agreed intervals
Clarifying questions
Response requested within one business day
If timelines shift
You are notified before changes are applied
Scope questions
Raised before delivery proceeds — not after
Two ways to start
Ready to submit a direct request
- Your requirements fit a pre-scoped package
- You are comfortable with fixed-scope delivery
- You want to start promptly after scope is confirmed
Not sure which package fits
- Your requirements may need custom scope
- You want to combine multiple services
- You want to discuss before committing
No public commerce or intake
No public payment methods
Information and proposal-stage discussion only. Selected services display informational USD prices; a written proposal confirms scope, any applicable taxes, third-party costs, and commercial terms. No checkout, payment, intake, or work-start authority is provided on this route.
- Credit/debit cards (Visa, Mastercard, Amex)
- Bank transfers
- Additional methods may be available — contact us to confirm
No delivery activation from this route
Delivery, if ever offered, requires a separate written scope and authorization.
- 1.Verified payment confirmation
- 2.Intake completion (confirms scope, deliverables, and timeline)
No work begins before verified payment. Delivery timing and any separately scoped specialist work are confirmed during intake and documented in writing.
Timeline Approach
All timelines confirmed during intake based on your specific requirements:
- Security reviews: Timeline depends on asset count, complexity, and package tier
- App development: Timeline depends on platform count, feature scope, and integration requirements
- Advisory services: Recurring monthly sessions
Frequently Asked Questions
Ready to get started?
Use email for non-sensitive proposal-stage communication.
For strategic app product partnerships — Apply for Partnership