A website that feeds sales.
A clear view in Power BI.

Follow an enquiry through the ecosystem.

An illustrative digitisation enquiry shows how the proposed connections work. This is a workflow example, not a live lead or a statement that accounts are already connected.

What lives where.

Connecting the ecosystem does not require copying every platform metric into Ruddr. Each tool keeps the records it is responsible for; shared identifiers connect the management view.

The six dashboard views and the decisions they support.

The report pages are designed around decisions, with available data and role-appropriate access confirmed during onboarding.

How we handle an exception.

A connected system also needs a visible recovery process.

The connected growth system

Build a new Integra website around clear service offers and relevant enquiries. Connect its forms to a secure lead intake service and Ruddr sales workflow. Bring acquisition, sales and delivery data together in Power BI so leadership can follow enquiries through to won projects and financial results.

Proposed architecture: website and platform lead forms → secure intake and attribution store → Ruddr companies, contacts and sales pipeline → reporting dataset → Power BI. Google, LinkedIn, Meta, website analytics and email results also feed the reporting dataset directly. Ruddr remains the sales and delivery workspace; Power BI is the combined reporting destination.

Implementation begins with an account, licence and access review, followed by the agreed website, integration and reporting delivery. Integra retains ownership of its accounts, website content and business data.

A full website build

Sitemap: Home; About and team; information governance; Microsoft 365 and SharePoint; digitisation and scanning; energy and engineering information; customer stories; insights and blog; resources and webinars; contact and project enquiry; privacy and cookie information; and a useful 404 page. Confirm the final service structure with Integra before design.

Deliverables: mobile-first RainRocks design for Integra, reusable service and campaign landing-page templates, an editable CMS, approved copy and imagery, resource and webinar templates, site search where justified, accessible navigation, fast images, metadata, canonical URLs, sitemap and structured data where applicable. Migrate approved existing content and preserve valuable URLs through a tested redirect map.

Forms: consultation request, project brief, resource or webinar registration, and separate newsletter signup. Show a clear next step after submission. Notify the assigned owner and retain the enquiry even if a downstream system is unavailable. Do not treat a resource download as a sales opportunity automatically.

Before launch: test forms, routing, duplicate handling, consent controls, keyboard access, mobile layouts, analytics events, redirects and search indexing. Train editors, document ownership, take a backup and agree a reversible launch plan.

Ruddr sales pipeline setup

Build on Integra’s existing Ruddr system with a sales workflow that connects contacts, opportunities and delivery projects. Confirm the existing plan and access during onboarding so only necessary licence changes are proposed. [S26 S31]

Proposed workflow: Incoming enquiry → Qualified → Discovery → Scoping → Proposal sent → Negotiation → Won or Lost. Keep unqualified, spam and nurture records outside the active opportunity forecast. Confirm which stages and fields can be configured in the workspace before migration.

Incoming: validate the request, source and owner. Qualified: sales confirms company fit, a relevant need and a next action. Discovery: record the business problem and stakeholders. Scoping: agree the proposed engagement and delivery input. Proposal: record the value, issue date and follow-up. Negotiation: record the decision date and blockers. Won: confirm the agreement and hand over to a delivery project. Lost: capture a reason; nurture only with an appropriate communication basis.

Require a company, contact, owner, service interest, source campaign, next action and due date. Add estimated CAD value and expected close date once the engagement is scoped. Use sales-approved probabilities for weighted pipeline, and distinguish estimated contract value from recognised revenue. Keep campaign attribution in the linked intake store when native fields are unavailable.

Sales responds within one business day, reviews overdue next actions weekly, and reviews stage ageing and lost reasons monthly. Link a won engagement to the client and project so delivery can plan capacity and finance can report actual revenue and margin.

Integration setup includes validation of supported company, contact and opportunity updates. Where automatic opportunity creation is unavailable, a tracked sales task and a reconciled opportunity link provide the agreed handoff. Access and connector requirements are confirmed during onboarding. [S32]

Forms and reliable lead routing

Capture name, business email, company, service interest and enquiry details, with phone optional. Capture consent separately for newsletters. Store submission time, consent wording version, landing page, referrer, original and latest UTMs, and permitted advertising click identifiers. Collect only fields that have a defined use.

Use server-side validation, spam protection, a unique submission ID and a durable queue. Match companies and contacts carefully, retain multiple enquiries from the same person, and make retries idempotent. Keep a delivery audit, retry failures and alert an owner when intervention is needed. Keep API credentials on the server.

Send a receipt only after the enquiry has been saved. Route by service and account ownership, with a fallback sales owner. Test successful delivery, duplicates, an existing client, invalid fields, spam, a Ruddr outage and a failed retry. A failed CRM delivery must remain visible in an intake queue rather than silently losing the lead.

Acceptance test: one website enquiry produces one saved intake record, one appropriate contact or company match, an assigned owner, a recorded source and a visible sales next step. A replay must not create a duplicate. Keep personal information out of GA4 event parameters and URLs.

Ads analytics social and email connections

Google Search: CAD $800 monthly. Connect approved ad accounts, campaign IDs, costs and conversion definitions. Use GA4 and Google Tag Manager for consent-aware website measurement and Search Console for aggregate search queries and landing-page performance. Validate qualified-lead feedback through the currently supported Google route before enabling offline conversions.

LinkedIn: CAD $1,200 monthly. Start with one focused professional audience and one principal offer, testing creative without fragmenting the budget. Use website conversions or Lead Gen Forms as appropriate. Lead Sync access requires approval; use an approved connector or controlled first-party export if direct access is unavailable. [S34]

Facebook: CAD $0 paid initially, with the organic publishing plan retained. Connect authorised Page insights and post results where permissions allow. Enable remarketing or Meta conversion tracking only if the agreed measurement and consent setup requires it; tracking availability does not create a paid campaign.

Social reporting brings authorised company-page reach, engagement and clicks into Power BI. Publishing remains in the social platform or agreed scheduling tool, while explicit enquiries enter the sales workflow. Data coverage follows each platform’s permissions.

Email: connect the selected email platform for campaigns, consent, unsubscribes and engagement. Pass relevant requests to sales and aggregate campaign results to Power BI. Keep a central suppression process so a sales sync cannot resubscribe someone who opted out.

Use a consistent lowercase UTM convention for source, medium, campaign and content. Reconcile platform lead IDs with intake IDs. Retain first-touch and latest-touch fields separately, and label assisted conversions separately from primary attribution. Do not add overlapping platform conversion totals and call them unique leads.

Power BI reports and dashboards

Executive growth: monthly spend versus budget, valid and qualified enquiries, meetings, accepted opportunities, open pipeline and won business. Include source coverage and last successful refresh beside the headline measures.

Paid acquisition quality: LinkedIn versus Google spend, clicks, qualified leads, cost per qualified lead, meetings and opportunities by campaign. Show unavailable where the denominator is zero or data is missing. Review acquisition monthly and follow opportunity outcomes over at least 90 days.

Website and content: landing pages, traffic sources, enquiry completion, resource downloads, search queries, article and social clicks. Keep website conversion rates within a consistent session or user definition; do not imply that an anonymous page view identifies a buyer.

Sales pipeline: value by stage, stage ageing, overdue next actions, forecast close dates, win/loss reasons and conversion over defined cohorts. Keep a snapshot or stage-change log from implementation onward so historical movement is measurable rather than inferred from the current stage.

Delivery and finance: won engagements linked to Ruddr projects, recognised revenue, actual costs, agreed margin definition, utilisation and capacity. Limit financial detail to authorised roles. Contract value, recognised revenue, cash receipts and advertising-attributed revenue must remain distinct.

Reporting combines campaign spend, website activity, unique enquiries, opportunity progress and project financials using consistent dates and identifiers. Reconciliation checks help prevent duplicate leads, spend or revenue from distorting the management view.

Implementation: use scheduled extracts or approved connectors into a Microsoft-hosted staging store such as Azure SQL, then a Power BI semantic model. Choose storage after volume, licence and access discovery. Start with daily refresh and expose refresh failures; higher frequency requires a confirmed business need and supported configuration. [S33]

Distribution: publish to a restricted Power BI workspace or app with appropriate viewer and author licences. Confirm Pro, PPU or capacity requirements for the actual audience before quoting. Financial dashboards must not use public Publish to web. [S35]

Delivery sequence costs and acceptance

Indicative eight-week sequence, subject to discovery and content approval: week 1 confirms scope, licences, access, data fields and baseline; weeks 2–3 approve design, sitemap and copy; weeks 3–5 build the website and intake; weeks 4–6 configure and test the Ruddr workflow; weeks 5–7 build the data model and Power BI pages; week 8 reconciles results, trains owners and launches with monitoring. API approval or content delays can extend this.

RainRocks owns web delivery and integration implementation; Integra appoints a sales process owner, service reviewers and a finance reporting owner. The Microsoft administrator approves access and dashboard distribution. Agree ongoing support, incident response and connector ownership before handover.

Implementation is CAD $13,505.90, followed by CAD $4,362.47 per month for managed delivery. Both service fees include the agreed 20% discount. Advertising is CAD $2,000 per month separately. See the Investment and monthly service chapter for the transparent breakdown and complete deliverables.

Go-live evidence: approved website pages and redirects; successful and replayed test enquiries; outage recovery; source attribution matched across forms and sales; one test opportunity progressed to a linked project; authorised dashboard access; daily refresh and failure alert tested; platform spend reconciled; and finance totals agreed. Use synthetic records for testing and remove or label them before production reporting.

First 90 days of media: LinkedIn 60%, Google 40%, Facebook paid 0%. Review enquiry fit and follow-up monthly, then compare accepted opportunities and pipeline after 90 days. Change the allocation using observed quality and commercial progress rather than click cost alone. LinkedIn is the primary test, not a guaranteed source of most leads.

Primary implementation references

What the connected system gives Integra.