PRODUCT SCHEDULE — BEYOND PULSE
Draft prepared for attorney review. Drafted 09/09/2026. Risk rating R2. The prices and the seat rules were confirmed on 10/09/2026 and are no longer provisional.
Version 1.1 · Effective 9 September 2026
What changed in 1.1. Two things, and neither alters what is charged. The prices in clause 3 carried a warning that they were awaiting confirmation; they have been confirmed, and the warning is gone. And the plan limits in clause 3 are now enforced by the Service, as clause 2.4 of the Master Terms says they are — when this Schedule was first published the product had no notion of a plan at all, so every workspace had every feature whatever it was paying for.
This is the Product Schedule referred to in the Beyond Master Software Terms. It forms part of that agreement. Where it conflicts with those Terms, this Schedule governs for Beyond Pulse.
1. WHAT BEYOND PULSE IS
Beyond Pulse records the time your people spend, prices it against the rates you set, and tells you what each project, client and person actually costs and earns.
It does four things:
- Time. A timer, manual entries, a week grid, and timesheets that get submitted and approved.
- Money. A cost rate and a charge rate per person, dated so that changing a rate never restates work already recorded. Hours become cost, revenue, gross profit and margin.
- Invoicing. Billable time and expenses into an invoice, with clients, payment terms and expenses.
- Corroboration. An optional activity signal — see clause 6, which is the part that needs reading properly.
2. SEATS
2.1 A Seat is one active person in your workspace. Somebody marked inactive does not consume a Seat.
2.2 Your Seat count is measured on the day your invoice is raised.
2.3 A Seat added mid-month is charged pro rata from the day it was added. A Seat removed mid-month is not refunded for that month and stops counting from the next cycle.
2.4 There is no minimum number of Seats.
3. PLANS AND PRICES
No VAT is added — Beyond is not a registered VAT vendor (clause 4.2 of the Master Terms). The limits in this table are enforced by the Service, as clause 2.4 of the Master Terms says. A feature with no tick on your plan is refused rather than merely hidden, and the refusal names the plan you are on and the plan it needs.
| Professional | Business | |
|---|---|---|
| Price | R95 per Seat per month | R130 per Seat per month |
| Billed annually | ~20% less | ~20% less |
| Time, projects, clients, activities, tags | ✓ | ✓ |
| Billable rates, expenses, budgets and alerts | ✓ | ✓ |
| Client invoicing, timesheets | ✓ | ✓ |
| Time off, approvals, team timesheets | ✓ | |
| Activity signal, ClickUp integration | ✓ | |
| Profitability and margin | ✓ | |
| Bonus scorecards | ✓ |
Enterprise — volume pricing and anything bespoke, on request and by separate written agreement.
There is no free tier. Beyond Pulse is paid from the first Seat after the trial.
4. TRIAL
4.1 The Trial Period is 7 (seven) calendar days from the day your workspace is opened.
4.2 During it the Service is free and is provided without warranty, as clause 5.2 of the Master Terms says.
4.3 If payment arrangements are not in place when the Trial Period ends, your workspace is suspended, not deleted. You keep read and export access. Clause 11 of the Master Terms applies.
5. WHAT IS PROCESSED
The categories of Personal Information Beyond Pulse holds are listed in Annexure A of the Beyond Operator Agreement. That annexure is the authoritative list for this product.
6. THE ACTIVITY SIGNAL — READ THIS BEFORE YOU ENABLE IT
6.1 Beyond Pulse can record a coarse activity signal from a person's workstation, to corroborate recorded hours. It is off unless you enable it, and it requires software to be installed on each machine.
6.2 What it collects, and this is the complete list:
- the date and the machine's name;
- minutes the machine was in use;
- minutes it was running but idle;
- coarse category totals, such as
editor 210, browser 62, communication 40.
6.3 What it never collects, and cannot be configured to collect:
- window titles, document names and URLs — the field exists in the underlying data and is discarded at the boundary; there is no setting that turns it on;
- screenshots — none, ever;
- keystrokes — not recorded in any form;
- individual application names — the machine works out that a given program is an "editor" and sends only the category.
6.4 These limits are enforced by automated checks that fail Beyond's build, not by policy alone. The server is built so that it cannot accept a window title, a URL or an application name even if something tried to send one.
6.5 Coding time is opt-in per person. Each individual connects their own account. There is no administrative way to connect it for somebody else.
6.6 The activity signal never feeds a bonus scorecard. It corroborates hours. It is not a performance score and the product does not use it as one.
6.7 Before you enable it you must issue the monitoring notice Beyond supplies, to every person whose machine it will run on, and give them a chance to ask questions. That is your obligation as Responsible Party under section 18 of POPIA — see clause 2.5 of the Operator Agreement and clause 5.4 of the Acceptable Use Policy.
6.8 A day with no activity data is recorded as no data, never as zero.
7. RETENTION
7.1 You set your own retention period for activity data, between 7 days and 5 years. The default is 2 years.
7.2 There is no "keep forever" option, deliberately. POPIA section 14 does not permit retaining Personal Information for longer than is necessary, and an interface that offered indefinite retention would be inviting a breach of it.
7.3 Data past your retention period is deleted automatically by a scheduled job that runs daily.
7.4 Aggregated project totals — which identify no individual — are kept for as long as the financial records they support.
8. SUPPORT
8.1 Support is by email to Info@beyondic.co.za, during business hours, 09:00 to 17:00 SAST, Monday to Friday excluding public holidays.
8.2 Target acknowledgement times, which are targets and not warranties:
| Severity | What it means | Acknowledged within |
|---|---|---|
| Critical | The Service is unavailable, or figures are demonstrably wrong | 4 business hours |
| High | A significant function is unusable, with no workaround | 1 Business Day |
| Normal | Everything else | 3 Business Days |
8.3 Support access to your workspace is governed by clause 7 of the Master Terms and clause 6 of the Operator Agreement.
9. AVAILABILITY
9.1 No uptime percentage is warranted for this version, and stating one we have not measured would be worse than stating none.
9.2 We will give reasonable notice of planned maintenance and will schedule it outside business hours where we can.
9.3 If Beyond ever offers a service-level commitment with credits, it will be a separate written agreement.
10. DEPLOYMENT
10.1 Beyond Pulse may be provided hosted by Beyond or installed on the Customer's own infrastructure, as agreed in writing.
10.2 Where it is installed on the Customer's own infrastructure, the Customer is responsible for the security, backup and availability of that infrastructure, and clause 5 of the Operator Agreement applies to the Customer's own operation of it rather than to Beyond's.
For the attorney reviewing this
- Clause 3, the prices. Commercial figures, not yet confirmed. Flagged in the document itself so nobody publishes it thinking they are settled.
- Clause 6, the activity signal. This is the highest-risk part of the product for POPIA. The drafting deliberately states the negative list as strongly as the positive one, and says the limits are enforced in code. Please confirm the section 18 obligation is correctly placed on the Customer in 6.7, and that 6.6 is worth stating as a contractual term rather than only as a fact.
- Clause 9.1, no uptime warranty. Please confirm this is defensible against a Consumer Protection Act claim by a small-business customer under section 54, given that the Service is supplied for a fee.
- Clause 10.2. Where the Customer self-hosts, Beyond arguably stops being an Operator at all. Please advise whether the Operator Agreement should be disapplied in that case rather than partially redirected.
schedule-pulse · v1.1 · sha256 2dca0719d0f0f58626d98d1ef3d3e7a150172f4288e51fe84695aefc8c66a787