Before you build anything.

We design intelligence and automation systems around how a business works: finding opportunities, supporting sales, understanding customers and growth, improving management decisions, and making approved company knowledge easier to use. The scope can be one module or several connected systems.

Suitable growing companies across product, service, project, retail, ecommerce, manufacturing, professional services, software and subscription models. Suitability depends on the problem, useful evidence, process ownership and whether a system is commercially justified.

No. PCI may work with B2B, B2C, B2B2C and mixed-model businesses. The signals and customer journey should fit the business rather than assume every company sells through quotes or a traditional sales team.

No. They are connected options, not a compulsory platform bundle. One module may be enough, and a new system may not be justified at all.

AI may be part of an implementation, alongside research, existing software, automation and human judgement. We start with the commercial question and evidence, then choose suitable methods. An AI tool is not the starting requirement.

Only where there is a clear agreed reason. We prefer improving or connecting an existing tool when it already does the job. The assessment may recommend a process change with no new PCI build.

Potentially. Access, available integrations, data quality, provider limits and the exact workflow must be checked during scoping. We do not promise compatibility with every tool before that review.

Yes. Start with the smallest worthwhile improvement, test it, and connect more only when useful. Accepted shared foundations should not need to be rebuilt or purchased twice; new scope and any necessary changes are agreed separately.

An optional layer that combines selected customer, sales, owned-performance, search and public market evidence to identify patterns, changes and possible next actions. Recommendations remain subject to human review.

A private interface for the approved intelligence and knowledge a team needs. It can provide source-linked answers and reviewed briefs with role-based access. It is an implementation direction that is scoped and tested, not an unrestricted universal agent.

An optional ongoing service covering the agreed maintenance, monitoring, recovery, testing, minor tuning and eligible improvements to reusable modules you already use. Substantial new integrations or business functions are separately scoped.

A PCI-hosted model can be scoped: PCI operates the agreed runtime while client data, credentials, permissions, provider accounts and usage limits remain client-specific. The operating responsibilities are confirmed before implementation.

Yes, where the proposed system and your environment are suitable. In a client-hosted model, PCI installs or configures the agreed system in infrastructure or provider accounts you own. Access, support and handover responsibilities are agreed.

Third-party model/API usage, software subscriptions, data services and hosting may be paid directly by the client and are separate from PCI implementation and maintenance where applicable. PCI does not promise unlimited third-party usage.

No. Josh manually reviews the assessment before a personalised PDF is delivered. It can recommend an existing-tool improvement, no new system, one module, connected systems or further discussion. There is no automatic purchase decision or obligation to commission a build.

No. Qualification means assessed against agreed criteria, not guaranteed buying intent, contact permission or a sale. Commercial outcomes and search rankings depend on factors a system cannot control.

Implementation is scoped and quoted after the problem, current systems, evidence, integrations, ownership and acceptance criteria are understood. The assessment does not calculate supplier pricing. The agreed scope and price are confirmed before implementation.

Assessment handling follows the adopted PCI privacy notice: Josh-only Tally and restricted PCI Google Workspace processing, manual reviewed PDF delivery, and recorded retention/deletion rules. Identifiable assessment submissions are not sent to external AI services. Any later client implementation needs its own agreed access, sources and data boundaries.

No. The assessment's marketing checkbox is separate, optional and unticked. You receive the same assessment whether you consent or not. No marketing email programme is active; permission can be withdrawn at josh@phillipscommercial.co.uk.

Real collection is currently closed while the restricted PCI operating setup and public access are verified. The assessment page will show when it opens. You can discuss a specific improvement by email without sending confidential records or credentials.

You create the required provider account or dedicated project, add your billing and approve a secure connection with minimum necessary access. Where a credential is needed, use the agreed secure method. Never email passwords or API keys.

PCI does the preparation and you confirm what matters. We use the assessment to prepare an initial scope, then ask only for the decisions and access needed by the agreed system. Relevant details are confirmed before tools are connected.

Not as a blanket policy. Reusable improvements are versioned and tested, then checked for compatibility. Eligible changes follow the agreed review and deployment process; private data, configuration, permissions and knowledge remain separate.

No. Competitor work uses publicly observable evidence and clearly identified inferences. It does not imply access to private analytics, sales figures or internal systems.

No. Customer Intelligence can be useful on its own. A business might need a review of complaints, onboarding or product friction without any content workflow. Content is scoped only where it serves a real need.

The cross-industry architectures are illustrative, and the anonymous engineering example is a current build being developed and tested in stages. Optional capabilities are scoped and validated before reliance; they are not claims of universal production readiness.