Company identity
Final registered-company details, trading name wording, address/contact route, and ownership statements need human review before publication.
Local launch-candidate review
A calm pre-launch checklist before HighCaliberTrading.co.uk goes public.
This local page gathers the remaining business-site checks into one review surface. It is not published, does not approve launch, and does not connect DNS, hosting, analytics, contact forms, payments, customer data, installer uploads, or public indexing.
Current state: static planning information only. Launch remains blocked until explicit approval, final legal/company wording, provider-readiness review, and a deployment plan are confirmed.Readiness lanes
What must be green before public deployment is even considered.
Legal and policy copy
Privacy, terms, refund/cancellation, delivery/re-download, support boundaries, and no-guarantee recovery wording need legal/accounting review.
Merchant readiness
Lemon Squeezy remains the first-choice provider when approved. This page only prepares evidence and copy; it does not connect checkout or APIs.
Support path
Support and contact copy exists locally, but real forms, inbox routing, CRM, ticketing, and customer-data collection remain disabled.
Product separation
The business site must stay separate from product checkout pages, affiliate assets, customer accounts, and project-acquisition pages.
Pricing and licence structure
Own-site licences, free maintenance updates, optional paid extras, Apple/Android routes, and whole-project asset discussions need one reviewed structure before public pricing or checkout appears.
Deployment safety
DNS, hosting, analytics, indexing, installer uploads, signing, notarization, and remote pushes require explicit approval and a documented rollback plan.
Six-hour build board
Today’s local build-push board now ties the homepage proof cards, customer route, product purchase-page drafts, and software-asset lane into this launch review without changing publication status.
Local app smoke bundles
Aperture, Bento, and BlackBerry now build into unsigned debug macOS app bundles for local Finder review. They are not signed, notarized, uploaded, sold, or release-approved.
Lemon Squeezy readiness cockpit
The Lemon readiness page now shows the next-week mapping path for products, licences, optional extras, webhooks, customer portal handoff, and delivery gates.
Phone support readiness
A dedicated customer-service telephone route is now a launch goal: business number, AI/Hermes first-line triage, ticketing, privacy rules, and escalation-only handoff to Bryn.
Focused build-push review
What changed locally in the current six-hour build lane.
Business trust laneThe homepage, launch review, and whole-stack review now present the local build board, proof cards, parent-site readiness, legal/policy review gaps, and separated approval gates before public launch.
Customer route laneThe customer portal preview now includes entitlement thinking, provider abstraction, future download-safety checks, release-note handoff, checksum planning, support routing, and product-separable records without login or customer data.
Product purchase-page laneAperture, Bento, BlackBerry, and MindBridge purchase-page drafts carry compatibility-question prompts, clearer “what the customer gets” sections, release-readiness notes, and disabled checkout language.
MindBridge launch-template laneMindBridge is being polished as a reusable launch template: own-site first, optional Apple/Android routes later, professional report-pack upgrade path, and explicit no-upload/no-store-action gates.
Recovery packaging laneRecovery app packaging readiness is now tracked separately from publishing: local smoke tests, release notes, checksums, platform wording, signing/notarization status, and installer upload gates must be reviewed before any release action.
Asset-sale laneWhole-project asset positioning stays separate from ordinary app buyers and continues to use safe readiness and transferability language, not finance-style, unsupported-performance, or unsupported-outcome claims.
Pricing and licence review
Commercial structure to decide before any live offer exists.
Own-site desktop licencesPrimary direct-sales route for downloadable desktop products, using Lemon Squeezy first when approved. Public product names, price bands, licence terms, refund/delivery wording, checksums, and re-download rules still need review.
Free maintenance updatesBug fixes, compatibility upkeep, and safe minor improvements should be treated as part of the base customer promise, not as forced paid extras.
Optional paid extrasPaid modules should be genuine extra value such as advanced exports, professional reporting, batch automation, or business workflow packs, with entitlement rules decided before provider mapping.
Apple and Android routesApp Store, Mac App Store, iPhone/iPad, and Android routes can be additional channels where practical, but they do not replace own-site sales, Lemon Squeezy direct downloads, customer portal, affiliate flow, or software-asset sale planning.
Whole-project software assetsAcquirer language must stay separate from normal customer pages and avoid finance-style, unsupported-risk, or unsupported-outcome claims unless records and review support them.
Recommended next actions
Highest ROI work before public launch.
- Review the local homepage, About, Portfolio, Privacy-first standards, Support, Delivery/re-download, Refund/cancellation, Terms draft, Contact draft, Merchant readiness, Lemon Squeezy readiness, Upgrade revenue, Software assets, and this launch review page.
- Use Whole-stack review to keep the business site, apps site, customer portal, affiliate portal, recovery apps, MindBridge, Lemon Squeezy readiness, upgrade planning, and software-asset lane aligned.
- Use the local pre-launch decision memo at
HIGHCALIBERTRADING_CO_UK_PRELAUNCH_DECISION_MEMO.mdas the current plain-language human review pack. - Replace placeholder legal/company details only after the final registered-company wording and review notes are available; use
COMPANY_DETAILS_DISPLAY_STANDARD.mdas the local checklist. - Prepare professional phone support using phone support readiness: choose a dedicated business number, ticketing route, AI/Hermes triage script, privacy wording, and escalation rules before publishing any telephone number.
- Keep product sales pages and whole-project acquisition pages separate so normal buyers do not see confusing business-asset sales copy.
- Review the pricing/licence structure in the memo before adding public prices, checkout copy, Lemon Squeezy products, Apple/Android listing text, or acquisition-review enquiry routes.
- Prepare a launch decision memo from local validation results; do not publish or connect services from this page.
- Confirm recovery-app packaging readiness locally only: package smoke tests, release-note drafts, checksum plan, platform-support wording, and signing/notarization status must be reviewed before any installer upload.
- Open the private local review app bundles for human QA before treating any recovery app as release-ready; do not publish installers until packaging, signing, checksums, and support wording have been approved.
- Use Lemon Squeezy readiness as next week's integration cockpit, but do not create/connect products, API keys, webhooks, checkout links, customer records, or delivery files without explicit approval.
- Capture Chrome visual-QA evidence for the launch review, whole-stack review, customer portal, MindBridge page, and recovery app surfaces before public deployment is considered.
Approval gates
This page deliberately keeps commercial actions disabled.
No publishingNo hosting, DNS, public deployment, search indexing, or remote push is performed by this prototype.
No trackingNo analytics, pixels, cookies, or external measurement scripts are connected.
No customer dataNo live contact form, support inbox, CRM, account login, or file upload path is connected.
No commerceNo Lemon Squeezy, Paddle, Stripe, checkout link, licence enforcement, installer upload, or payment flow is live.