Package 1 Explained: One Energy ESG Workspace, Four Operating Tracks

Package 1 is one controlled energy ESG workspace that organizes utility evidence, review status, Scope 2 calculation context, reporting handoff, and approved LinkedIn-ready drafts across four operating tracks.

Core Ingestion at $5,400 per year is the starting track for a team that needs a defined workspace, approved reporting-period narrative, static brand graphic support, and a review-ready energy summary without continuous provider ingestion.

No universal direct-loading promise is made. Package 1 can produce a Workiva-ready package with structured rows, mapping information, manifest, evidence hashes, and review status. A direct Wdata API connector would require customer-specific Workiva authorization, tenant configuration, mapping, testing, and a separately approved integration scope.

No. IRS guidance describes ordinary and necessary business expenses as a general framework. The customer’s facts, agreement, service period, accounting method, records, capitalization questions, and adviser analysis determine the appropriate treatment.

No. The LinkedIn Executive Communications layer creates governed drafts and approved graphics or copy for manual client use. Client review remains required, and the system does not automatically post, message, impersonate an executive, or guarantee reach, leads, coverage, or conversions.

After a verified payment event reaches the server, the payment workflow can validate the selected Package 1 track, retain the track and commercial record, and provision or activate the corresponding isolated workspace context. The browser does not bypass server-side validation, tenant boundaries, identity checks, or any required agreement controls. Provisioning is therefore designed to be prompt after a valid event, but the public article does not promise that every payment creates a fully configured production workspace without onboarding steps.

Track 02 uses an evidence-hash approach to help detect repeated inputs, support idempotent processing, and preserve integrity references when controlled provider data is accepted. A matching input can be recognized rather than recorded as a new duplicate, while corrections are retained as new versions instead of silently overwriting prior records. Hashing is an engineering control; it is not an IRS certification, an assurance opinion, or proof that a subscription is deductible under Section 162. The customer and its advisers remain responsible for the applicable tax and accounting analysis.

No product can declare a customer’s tax treatment or guarantee IRS compliance from a hash alone. Track 02 can preserve source context, processing status, review decisions, correction history, evidence references, and audit events in a structured operational record. Section 162 and related accounting rules require a customer-specific review of business purpose, ordinary and necessary status, service period, records, capitalization, and applicable law by qualified professionals.

Not as a universal promise. Track 03 produces a Workiva-ready package with approved rows, mapping information, period and unit context, manifest data, evidence references, export signature metadata, and review status. A direct Wdata API workflow may be scoped for a specific customer only after Workiva tenant authorization, OAuth credentials, table schema, mapping, security review, and acceptance testing. Even then, customer-side mapping or approval may remain necessary; the current public Package 1 promise is a controlled handoff, not guaranteed zero-touch native synchronization.

Reporting Sync is priced at $15,000 per year for the defined Package 1 software and governed workflow scope: approved multi-period calculations, Workiva-ready handoff structure, mapping context, evidence references, and reporting narratives. It is designed to reduce repeated spreadsheet reconstruction and coordination work through a self-serve client workspace and server-controlled automation. Watershed publicly positions itself as an enterprise sustainability platform and directs buyers to request a demo; we do not rely on a verified public Watershed price or claim that every customer would pay $50,000 or more. The comparison is about scope and operating model, not a guarantee of savings or a claim that the products are equivalent.

Reporting Sync is intended for finance, ESG, sustainability, accounting, procurement, and reporting teams that need approved outputs across multiple periods and a documented handoff into an existing reporting process. It is a fit when the organization values structured evidence, review status, mapping context, and repeatable delivery more than a one-off spreadsheet or an open-ended consulting engagement.

Track 04 is designed for authorized operators that coordinate more than one workspace. Each tenant context is associated with its own workspace identity and access boundary, while the Founder or authorized operator can switch contexts through protected administrative tools. The architecture is intended to prevent one client ledger from being exposed to another. The exact number of entities, users, response commitments, and operating services must be defined in the executed commercial scope; the track price alone is not an unlimited-entity or automatic SLA promise.

The system uses server-side authorization, workspace and tenant identifiers, scoped queries, role controls, and policy tests to keep client records separated. Founder-only tools can operate across authorized simulation or administrative contexts without making those records visible to ordinary clients. Isolation is a software control that must still be monitored, tested, and configured correctly; the article does not present it as a legal certification or a substitute for the customer’s security review.

The client follows the next action shown by the workspace: provide a reporting period and source document, confirm account or meter context, or authorize a controlled provider connection when its track and configuration support that path. The internal workflow handles validation, coverage checks, correction-safe versioning, calculations from approved inputs, and handoff preparation. Client and Founder review gates remain in place where the workflow requires them.

No. Package 1 organizes evidence, workflow status, reporting context, and approved handoff materials. It does not provide tax, legal, accounting, engineering, assurance, or regulatory advice; it does not certify emissions data; and it does not determine the customer’s filing position or environmental result. Customers should involve the qualified professionals appropriate to their facts and reporting obligations.

A spreadsheet can hold values, but Package 1 is designed around a controlled lifecycle: intake, validation, correction, approval, calculation, reporting, and handoff. It preserves review status, evidence references, source consistency, and version history so the client can see the next action instead of managing disconnected files and email threads.

The four tracks let an organization buy the operating depth it actually needs. Core Ingestion starts with a controlled manual workflow. Connected Framework adds authorized provider operations. Reporting Sync adds multi-period handoff structure. Professional Operator adds governed coordination across authorized workspaces. This keeps the public choice simple while allowing the internal system to scale in a controlled way.

The client is not asked to operate the evidence ledger, factor versioning, provider adapters, or export controls. The workspace presents a clear next action, the required input, the review state, and the resulting deliverable. Complexity stays inside protected workflows while the client receives a focused path from source evidence to approved report or handoff.

Core Ingestion is intended to provide a bounded starting path for a team with one accountable owner and a defined reporting period. It can begin with controlled manual evidence and a review-ready summary. Any additional provider connection, multi-period scope, tenant configuration, or operating service should be confirmed in the commercial scope rather than assumed from the entry track.

Connected Framework adds a controlled path for an authorized utility-provider connection, subject to credentials, OAuth scopes, account and meter matching, fail-closed controls, and Founder or authorized review gates. It is intended for teams that want a repeatable operating rhythm without exposing provider secrets or raw operational telemetry to ordinary client users.

Reporting Sync adds delivery structure around approved calculations. The package can include multi-period rows, mapping context, unit and period information, manifest data, evidence references, export signature metadata, review status, and stakeholder narratives. This helps reporting teams move from a calculated result to a documented handoff without reconstructing the supporting story from scratch.

Professional Operator is designed for an operator, holding-company function, or enterprise program office that coordinates several authorized workspaces and needs consistent communication standards. Its value is governance and repeatability across approved contexts, not an unlimited number of entities, an automatic SLA, or unrestricted access to every client record.

The current Package 1 public price points are fixed annual planning prices: $5,400 for Core Ingestion, $9,600 for Connected Framework, $15,000 for Reporting Sync, and $24,000 for Professional Operator. API connections and data volume influence the appropriate operating scope, but the client-facing value is the governed workflow and deliverable, not a raw API-count meter. Additional scope belongs in a separately confirmed agreement.

Package 1 is positioned as a focused energy ESG workflow with transparent annual track prices rather than as a claim to be the cheapest or equivalent to every enterprise climate platform. Buyers should compare the included workspace, source coverage, review controls, calculation scope, handoff format, support terms, and implementation needs. The practical value proposition is a clearly bounded product workflow with visible pricing and less reconstruction work for the defined scope.

The layer prepares evidence-linked executive communication drafts and approved graphic or copy concepts appropriate to the selected track. Core Ingestion focuses on a reporting-period narrative and static brand support. Connected Framework adds persona-oriented explanations of approved intake and data-quality progress. Reporting Sync adds stakeholder narratives around the handoff. Professional Operator adds consistent language across authorized workspaces. Client review and manual copying remain required.

It turns approved operational progress into a reviewable communication asset without promising reach, media coverage, leads, conversions, or executive endorsement. The value is consistency, speed of drafting, evidence-safe language, and alignment between the reporting workflow and the message a stakeholder may choose to publish manually. External use remains controlled by the client’s review process.

Yes, the content templates can be oriented to different stakeholder questions while remaining grounded in approved workspace context. A CFO-oriented draft can emphasize scope and review records. A sustainability draft can explain approved energy-data progress. An operations draft can focus on intake and quality workflow. A procurement draft can explain deliverables and governance. The system does not impersonate a person or invent results for any audience.

No. Public content and governed drafts are designed to avoid raw telemetry, credentials, protected locations, meter identifiers, account identifiers, infrastructure details, and other sensitive operational data. Communication drafts should use approved summaries and review-safe context. Private client data remains inside the authorized workspace boundaries.

The buyer can point to a defined annual track, a specific workspace scope, a visible next-action experience, documented review controls, approved reporting outputs, and a Workiva-ready handoff path where applicable. The product description separates software workflow from professional advice and tax conclusions, giving finance, procurement, sustainability, and operations stakeholders a clearer basis for their own review.

Choose Core Ingestion if the priority is a controlled starting workspace. Choose Connected Framework if authorized recurring utility data is central. Choose Reporting Sync if approved multi-period delivery and Workiva-ready handoff matter most. Choose Professional Operator if an authorized operator needs consistent governance across multiple workspaces. The choice should follow the operating requirement, not the number of marketing features alone.