Monitoring What Matters.
Every objective. Every project. Defined, classified, monitored.
Most project management tools treat every task, action, and milestone as equal weight. They give you a long list of things to track, and you decide what’s urgent. The result is noise. The catastrophic items get blindsided by the trivial ones, and the trivial ones consume your morning.
PULSE works differently. Every project objective gets classified. Glass-ball means critical, the project breaks if you miss it. Rubber-ball means it matters, but the project can absorb it. That single classification changes what gets flagged, what gets escalated, and what gets quietly tracked. No other PM tool does this.
Glass shatters. Rubber bounces. Know the difference.
Before PULSE tracks what’s happening, it asks you to define what matters. Project Initiation is a guided 15-minute flow that produces your Project Brief. The Brief is a formal document setting out the project’s vision, objectives, glass-ball and rubber-ball criticality, constraints, milestones, and stakeholders. Once that’s done, the rest of PULSE unlocks. The Action Log, Risk Register, Programme Tracker, and Executive Dashboard all read from the Brief.
15 minutes. Generates Project Brief.
PULSE works best when you start with Project Initiation. You can configure manually if you need to. But the discipline is what makes the rest of the product powerful.
PULSE is being built one module at a time. Each module shares the same glass-ball and rubber-ball spine. What you classify in Project Initiation drives what gets flagged everywhere else.
A guided 15-minute flow that produces your Project Brief. Vision, objectives, glass-ball and rubber-ball criticality, constraints, milestones, stakeholders. Exportable to PDF and Word.
The foundation everything else builds on.
Every open action across every project, classified against the glass-ball objectives from your Brief. Flagged automatically when an action threatens a glass-ball.
Structured risk capture tagged to glass-ball objectives. Mitigation tracked alongside the actions that close it.
Critical-path visibility with dependencies, float, and schedule impact. The institutional scheduler, finally built for developers without a PMO.
Cross-project health summary. Stakeholder-specific views. The view a JV partner, lender, or board member needs in one place.
Ten developers. Direct input into PULSE before it launches. First access to Project Initiation the moment it ships.
A 90-day programme. Working sessions while we build PULSE module by module. First access on every release. A direct say in what gets built next.
Two real projects, two hours a week, honest feedback. A willingness to shape PULSE before it is finished.
Lifetime founding-member pricing on PULSE. Priority access to every module as it ships. A direct line to the team building the product.
No payment. No commitment beyond the design partner programme. Ten spots total.
A two-bucket classification of every objective on your project. Glass-ball objectives are critical to project success. Miss one and the project has failed against what it was set up to deliver. Examples include completion date, planning consent retained, and GIA target. Rubber-ball objectives matter to delivery but won't break the project if they slip or change. Examples include supplier choice, fit-out scheduling, and finish specification. PULSE uses your classification to decide what gets flagged, escalated, or quietly tracked.
Because PULSE can only monitor what you've defined. Without a Project Brief, the Action Log doesn't know which actions are critical, the Risk Register doesn't know which risks threaten what, and the Programme Tracker doesn't know which milestones can slip. Project Initiation is a 15-minute flow. It is the discipline that makes everything else work.
Technically yes. You can skip ahead and configure objectives manually for each module. But you'll lose the system-derived suggestions, the over-constraint warnings, and the milestone templates. PULSE works best when you start with Project Initiation. The discipline is what makes the rest of the product powerful.
Generic PM tools treat every task as equal weight. They give you a long list to track, and you decide what's urgent. PULSE is built around a specific classification (glass-ball vs rubber-ball) that determines what gets flagged automatically. That framing doesn't exist in general-purpose tools or in the construction-specific ones. PULSE is the discipline of programme delivery, built into the workflow.
The Project Brief output is a PDF and a Word document. Your consultants don't need to use PULSE to read it. For modules that ask consultants to log actions or update risks, the interaction is a single click or a short comment. No training. If using PULSE is harder than sending a WhatsApp message, we've failed.
Project Initiation ships first to design partners in Q3 2026. Action Log, Risk Register, and Programme Tracker follow on the roadmap. Executive Dashboard is planned. Design partners get first access to each module as it ships.