You don't know what your team is actually doing.
It's the loudest complaint on every software team, and not because the team is sloppy. Every PM tool is built around the plan, not the pulse. sparQ Pulse is tactical project management for teams who live in GitHub: active work, standups, accountability, and delivery visibility, with status derived from your repo. Not roadmaps. Not portfolios.
Open source, AGPL v3. Get notified when the repo opens →
01 Lack of Visibility→
“My devs aren't doing what they planned. The PM tool's lying to me.”
r/projectmanagement·
02 Context Fragmentation→
“I can't find anything. It's all split between Slack, Drive, the PM tool, and GitHub Issues!”
r/projectmanagement·
03 App Switching Friction→
“I live in Slack and GitHub. Opening the PM tool is too much friction.”
r/projectmanagement·
Three reasons your team stops opening it.
Every PM tool fails the same way. Once you see the pattern, you can't unsee it.
Lack of Visibility
The plan is not the work.
Ask any tool who's blocked, who's heads-down, what shipped Monday. None of them can answer. That's the design, not a bug.
Context Fragmentation
The work is in six places at once.
Slack, GitHub, the drive, AI chats. The PM tool was supposed to sit above all that. It became one more place to forget to update.
App Switching Friction
Nobody leaves their tool to update a sixth one.
Every PM tool assumes the user will leave Figma, leave Slack, open the tracker, update a ticket, and come back. They don't. The tax goes unpaid.
PM tools were built around the plan. Your team works on the pulse.
The plan is what you intend. The pulse is what's happening. PM tools capture the first beautifully and the second not at all.
By week four, the tracker reflects what the team meant to do. The team is doing something else. That gap is the three evils, growing every day.
You can't fix this with discipline. The fix is to stop asking people to mirror reality into a second system, and instead derive the picture from where the work already lives. For software teams, that's Git.
The plan is what you intend. The pulse is what's happening. Most days, only the pulse matters.
sparQ Pulse runs on the pulse, not the plan.
Same category as Jira and Linear. Different organizing principle. Built around the three evils, derived from Git.
Derived status
Status comes from PRs, issues, and commits, not a field someone forgot to update. More accurate, more trusted, less work.
Tiny inputs
Standups, blockers, wins. Seconds-long gestures, not ticket ceremony. The team isn't asked to leave their day.
Git-native and open
Connect GitHub, reference issues inline, keep your repo as the system of record. Open source, AGPL v3, self-host free.
Open source, AGPL v3. Get notified when it opens ↓
Here’s what that looks like.
The first thing the team sees, every morning. Live presence on the left. Today’s standup in the middle. The active project on the right.
Who's in right now?
Today's standup
Today: v2 docs.
Blockers: None.
Blockers: Schema sign-off.
Project: Mobile App v2
10 seconds after you connect GitHub, your whole team has a daily rhythm.
Who's in right now?
Who's around. Who's heads-down. Who's out.
The first tab the team opens every morning, and the one they glance at twenty times a day. Available, in focus, blocked, out, on PTO. Every teammate's current state, live, no pinging required.
This is visibility, the first of the three evils, addressed at the team level. Focus mode silences notifications and signals heads-down to the rest of the team. PTO shows up where it matters, not buried in an HR tool nobody opens.
- Focus / Available status
- Team directory with profiles
- PTO and leave visibility
- Pulse check-ins
What's everyone working on today?
Today: Picking up the v2 docs.
Blockers: None, smooth day so far.
Today: Finish mobile reconnect logic.
Blockers: Need schema sign-off from Asim.
Daily sync without the daily meeting.
Project management doesn't start with a plan. It starts with what's actually happening today. Async standups, blockers with owners, action items with urgency tiers, all tied to repo activity.
Plans live here too, but they're a byproduct of the work, not the source of truth. Blockers aren't a comment in a thread. They're their own object, with an owner, a duration, and a nudge cadence. Nothing stalls silently for two days.
And the inputs are tiny: a two-minute prompt, not a ticket update. Reference any GitHub issue inline with #1234 and Pulse links straight to your repo.
- Async standups with team autofill
- Blockers with owners and nudges
- Action Items with urgency tiers
- Projects and tasks coupled to GitHub
- End-of-day digest
Project: Mobile App v2
The coordination that doesn't scroll past.
This is the fragmentation tax, paid down. Project posts, channels, DMs, the all-hands board, shared docs. Decisions stay where work happens, not in a thread that scrolls past.
When a teammate posts an update on a project, it's there tomorrow, next week, when the new hire joins. Not buried under sixty messages about lunch.
For larger organizations, Comm is the layer above the teamspaces. Org-wide announcements, the company calendar, cross-team DMs, the shared handbook.
- Project posts and team channels
- Direct messages
- Org-wide announcement board
- Shared docs, notes, and resources
- Company calendar
Can I finally see what my team is doing right now, without calling a meeting?
With sparQ Pulse the answer is yes.
#1234?sparQ Pulse goes public soon.
It's open source, AGPL v3, built in the open. Drop your email and we'll send one note the day the repo opens. No drip, no sales.
Launch-day email only. Unsubscribe anytime. Or watch the repo →
We have answers.
About sparQ Pulse
What is sparQ Pulse?
Is sparQ Pulse open source?
Does sparQ Pulse replace GitHub Issues?
#1234 inside Pulse and it links straight to your repo.How is this different from Linear or Jira?
Do I need to migrate anything?
# inside Pulse. Nothing moves. No re-linking, no re-tagging, no parallel tracker.Does it work with GitLab or Bitbucket?
What does sparQ Pulse integrate with?
Data and security
Where does my data live?
Can we export our data?
Stop running your team across six tabs.
sparQ Pulse is open-source, Git-native project management. Status derived from your repo, not from a field nobody updates. No second tracker, no migration.
Watch the repo → Open source, AGPL v3. Get notified when it opens · sparq@remarqable.io