Client-side approvals with audit trail
Clients approve deliverables inside the portal. Every approval is stamped with name, timestamp, and the exact file version they saw.
64%
PortalsETA mid Aug
Product / Roadmap
We ship on a schedule, not on a whim.
This is the same board our team works from. Items move left to right as they get built, every release is logged with a date, and anything we drop gets an honest note explaining why. No screenshots of features that don't exist.
Aug '25Jan '26Jul '26
ShippedThis monthPlanned
0Releases shipped in the last 12 months
0Median time from accepted request to production
0Customer votes counted on this board
0Items dropped this year, each with a public note
01
Now, next, and later
Three columns, strict rules. Now means engineers are actively committed and there is a build behind it. Next is scoped and scheduled. Later is accepted in principle with no date attached. Filter by area to see what is coming for the part of the product you use.
30 items
NowIn build
3Portal templates v2
Save an entire portal — tasks, folders, intake form, branding — as a reusable template and spin up the next client in under a minute.
45%
AutomationETA Sep
Inline file comments
Pin a comment to a page of a PDF or a point on an image, so feedback stops living in email threads.
30%
FilesETA Sep
NextScoped
3Multi-currency & local tax rules
Invoice in the client's currency with correct VAT/GST handling and a per-client tax profile.
BillingQ4 2026
Granular portal permissions
Decide per contact who can see billing, who can approve, and who can only view files. Useful when a client has several stakeholders.
PortalsQ4 2026
Task automations
Simple if-this-then-that rules: when a task moves to Done, notify the client, unlock the next phase, and start the invoice.
AutomationQ1 2027
LaterAccepted
4Native mobile app for clients
A read-and-approve companion app. The portal is already mobile-friendly, so this is about push notifications and offline files.
PortalsResearching
Proposals & e-signature
Send a proposal, collect a legally valid signature, and convert it into a live portal with the scope already filled in.
AutomationScoping
Bring your own storage
Point a workspace at your own S3 or Google Drive so files never leave infrastructure you control.
FilesResearching
Zapier & Make connectors
Now that API v1 is stable, we are building native Zapier & Make apps to connect LynxRise to your stack.
ApiIn design
02
Delivery timeline
Rough boundaries for what lands when. If an item slips, it stays on this chart and gets a red badge explaining why.
Q3 2026
Jul – SepClient-side approvals
Waiting on final design review.
AugPortal templates v2
Specced and scheduled.
SepInline file comments
Blocked by a dependency update.
SepQ4 2026
Oct – DecStripe connect integration
Accepted in principle.
OctClient intake forms
Accepted in principle.
NovCustom domains
Accepted in principle.
Dec03
Release history
Every named release and what it included, going back to the first private beta. We don't log minor bugfixes here, only features that change the surface area of the product.
v3.0
- Public REST API v1 & webhooks — Stable, versioned endpoints for clients, projects, tasks, files, and invoices.
- Recurring invoices & retainers — Set a monthly or milestone schedule once; LynxRise raises the invoice and notifies the client.
v2.9
- Custom domains with automatic certificates — portals now live on portal.yourstudio.com.
- Portal load time cut by 41% on file-heavy projects.
v2.8
- Team roles — owner, admin, member, and contractor with scoped project access.
- Bulk client import from CSV with duplicate detection.
- Fixed a bug where invited contacts on a custom domain received the wrong login link.
v2.7
- Branding controls — logo, accent colour, email sender name, and login background.
- Guided portal templates for agencies, consultants, and freelancers.
- Two-factor authentication for workspace members.
v2.6
- Files 2.0 — folders, versioning, and a 5 GB single-file limit.
- Task dependencies and per-phase due dates.
- Dropped: the built-in chat widget. Threaded comments on tasks and files covered the same need, and a second inbox made portals noisier. Existing chat history stays exportable until Dec 2026.
v2.5
- Invoice PDFs with your branding, sequential numbering, and tax fields.
- Client intake forms that create a project on submission.
- Daily encrypted backups moved to a 30-day rolling window.
v2.4
- Rebuilt the portal dashboard around project phases.
- Activity feed with per-client email digests.
- Audit log for workspace admins.
04
How something gets on this board
Votes matter, but they don't decide alone. A request has to survive four filters before an engineer is assigned to it.
request pipelineavg 11 days · accepted → production
Step 01Collected
From in-app requests, support tickets, and reviews. Duplicates are merged so the vote count reflects real demand.
Step 02Weighed
Votes, how many workspaces it unblocks, and whether it removes a manual workaround people are paying for elsewhere.
Step 03Scoped
Written as a spec with edge cases and a rough build estimate. If we can't scope it honestly, it stays in Later.
Step 04Committed
Assigned, dated, and moved to Now. From here it either ships or gets a public note explaining the change.
Where to send a requestEvery workspace has a Request a feature link in the help menu, and it lands in the same queue the team reviews each Monday. AppSumo lifetime-deal customers get the same weight as any other paying workspace — no separate tier, no second-class queue.
05
What we will and won't do
Being clear about the ceiling matters more than a long wish list. If one of the items on the right is a dealbreaker for you, LynxRise is probably the wrong tool and we would rather you knew now.
Commitments we hold ourselves to
- A named release roughly every two weeks, logged publicly with a date.
- Any feature that leaves this board gets a written reason in the release history.
- Breaking changes get 90 days' notice and a migration path.
- Features included in a lifetime deal stay included — we don't move paid features behind a new add-on.
- Your data stays exportable in open formats, whether or not you stay.
Things we're deliberately not building
- A full CRM with pipelines and lead scoring — we integrate instead of competing.
- Accounting and bookkeeping. Invoices, yes; a general ledger, no.
- An internal team chat product. Comments live where the work lives.
- Time tracking with screenshots or activity monitoring.
- AI features that write to client-facing content without a human approving it first.
06
What each status actually means
So a label on this page carries the same meaning every time you check back.
Now
Engineers assigned, code in progress, and a target release. Percentages reflect completed scope, not optimism.
Next
Specced with a target quarter. Not started yet, and the quarter can move by one — you'll see it here if it does.
Later
We agree it belongs in LynxRise. No date, no estimate, and it may be reshaped before it's built.
Beta
Live for workspaces that opt in. Functional and supported, but the interface may still change before general release.
A necessary caveatThis page describes current intent and is not a contract. Dates can move for good reasons — a security fix jumping the queue, an audit finding, or a scope discovery mid-build. What we promise is that changes appear here and in the release history, not that the plan never changes. Buy LynxRise for what it does today; treat anything in Next and Later as a bonus.
Missing something you need?
Send the request with a sentence about the workflow it would unblock. Those are the ones that make it to Now fastest.