NomadDeck
Watch the build. Own the result.
NomadDeck is the delivery cockpit for a software studio and the client portal in one. The studio tracks every engagement from discovery to live across a six-phase lifecycle, and each client gets a calm, branded window onto their own build, redacted to what they should see. The same screens serve both faces; only the data, the brand, and the gate change.
Not a video.The real app, live. No sign-up.
Local build on representative sample projects. The real project store is owner-entered and ships empty.
NomadDeck. Studio cockpit and client portal
By the numbers
- discovery to support, on one timeline
- 6 phases
- studio cockpit and client portal, one screen set
- 2 faces
- client-safe by construction
- Typed redaction
- public demo, staff cockpit, gated portal
- 3 hosts
discovery to support, on one timeline
studio cockpit and client portal, one screen set
client-safe by construction
public demo, staff cockpit, gated portal
Two faces, one build
The client sees their build. The studio sees everything.
The same screens serve both. Only the data, the brand, and the gate change, and the client view is built by reading only the client halves.
| Dimension | What the client sees | What the studio also sees |
|---|---|---|
| Progress | A calm, on-brand view of phase, milestones, and what ships next. | The same timeline, plus the internal notes and phase gates behind each milestone. |
| Money | Nothing. Cost and margin are internal-only. | Cost and margin on every engagement. |
| Risk | Only the risks that need a client decision. | The full internal risk register. |
| Cadence and team | Nothing. Cycles, bets, and who is assigned stay internal. | The Shape-Up cadence and the team's effort against estimate. |
| How the split holds | Reads only the client branch of each typed angle. | A new internal field is dropped from the client view by construction, never by an allowlist someone updates. |
Capabilities
What it does
- Every engagement at a glance
- The project list shows each engagement with its status and current phase, from prospect to delivered.
- A six-phase lifecycle
- Discovery, scoping, design, build, deploy, and support, each with its milestones and deliverables on one timeline.
- Studio cockpit and client portal
- The studio sees every angle, including cost, margin, and the internal risk register. The client sees a scoped, on-brand view of progress.
- Client-safe by construction
- Each angle is typed as client or internal, and the client view is built by reading only the client halves, so an internal field cannot leak by omission.
- Every project tool in one timeline
- Synced items from Jira, Confluence, GitHub, Linear, Asana, and Slack land in one project record as typed references, and only the client-safe ones reach the portal.
How the integration layer works
Every project tool in, one branded redacted timeline out
The studio keeps the tools it already runs. NomadDeck syncs them read-only into one unified project, redacts at read time, and serves the studio its full cockpit and each client a calm, on-brand window, with the studio's tooling never exposed.
The studio's tools
Connected read-only
JiraIssues and sprints
GitHubPull requests, releases
LinearTickets
SlackThreads
ConfluenceDocs
AsanaTasks
Scheduled sync
Read-only, no write-back
- Pull on a scheduleNormalized to references
- project_integrationsConnected sources
- external_referencesThe synced items
Redaction at read time
Typed, by construction
- One unified projectAll tools, one model
- Client-visible onlyRe-filtered on every read
Two faces
One screen set
- Studio cockpitTools and internals
- Client portalClient-safe references only
The aggregation model and the redaction are built and tested; the live scheduled sync against each tool's API is the next step. The studio's connected tools are internal-only and never reach a client.
Who it helps
One window each side actually wants
The same build serves the studio delivering the work and the client paying for it, with the line between them enforced by the types.
The delivery studio
The people building it
- Keep using Jira, GitHub, Linear, and the rest; they sync into one project view instead of being copied into status emails.
- See every angle: cost, margin, the internal risk register, the Shape-Up cadence, and the team's effort against estimate.
- A new internal field is hidden from the client by construction, so there is no allowlist to remember.
The client
The people paying for it
- A calm, on-brand window onto your own build: phase, milestones, and what ships next.
- Only the references that concern you, not the studio's internal tickets and threads.
- Approve deliverables and documents, and see the activity that matters, all under your own brand.
Architecture and security
Client-safe and client-owned
- Redaction by construction.
- Every angle is a typed client/internal split. The client view cannot contain an internal field, even one added later.
- Per-client session.
- Each client gets a scoped, signed session and ownership checks on every read and write. No client sees another tenant.
- Owned, not rented.
- A client runs their branded portal on their own cloud and domain. One build cost, no per-seat fee, no lock-in.
Try it
What you can try
Five minutes, no sign-up required.
- 1Browse the project list and see every engagement with its current phase and status
- 2Open a project and toggle between the studio face and the client portal face
- 3Notice what the client cannot see: cost, margin, and the internal risk register
- 4Step through the six-phase lifecycle timeline from discovery to support
Under the hood
How it works.
Want software built around your business?
Tell us the goal in your own words. We reply with a 60-minute call, an honest yes-or-no on whether we are the right fit, and a one-page sketch of how it could work. No obligation.
- Replies within one working day, usually sooner. Trinidad business hours (UTC-4).
- Your details stay between us. See the privacy notice.