Roadmap
A high-level view of what Fundly is building next, framed as direction rather than dated promises. Items are grouped by where they sit in the funnel: under active design, under active evaluation, or on the longer horizon.
Subject to change. Anything on this page can move — in either direction — as we learn from users and as scope firms up. Dated commitments (annual pentest, SOC 2 Type 1 roadmap, quarterly restore drills) live on /security, not here.
For features that have already shipped, see the changelog.
Actively building. These items have engineering work in flight or design close to final. Features can still slip, but the direction is firm.
Designing
End-to-end Spanish translations of the supporter-facing campaign pages, the checkout, and the public site (pricing, policies, security, status). The advisor dashboard remains English in this pass; we will localize the dashboard in a follow-up after we see how the supporter-side rollout is used in the field.
Designing
Today's OneRoster CSV import is the universal backstop. Native single-sign-on rostering through Clever and ClassLink removes the CSV step for districts that already use those systems, and keeps the roster fresh as students transfer in and out of classes.
Under active evaluation. We have read the case, talked to early users, and have a sense of what it would take — but scope, vendor, and timing are all open.
Evaluating
Most large-employer matching-gift programs accept a tax-id and a donation amount; surfacing that flow in the donor checkout is the leading candidate. We are weighing a first-party implementation against a partner; whichever path we choose, the supporter experience should not double the steps at checkout.
Evaluating
Product-sale campaigns today leave sales-tax collection to the organization. Stripe Tax is a credible way to delegate that — but only if it does not push the cost or the configuration burden back onto the advisor. We are pressure-testing that against small-org usage before we commit.
Direction we want to go, scoped but not yet scheduled. These are the items that change the product’s shape for bigger buyers.
Exploring
A district administrator seat that can see across every org the district supports, with read-only oversight of campaigns and payouts. The hard part is policy (what a district should be allowed to see, and what it should not) more than it is engineering.
Exploring
Saved filters, scheduled email exports, and per-program roll-ups so a district treasurer can stop exporting CSVs and merging them in a spreadsheet. The shape will be informed by what district buyers tell us they need in the first year of the multi-org tier above.
The honest answer is that prioritization is driven by what the field asks for. Procurement reviewers and school leaders are the two groups that move the product most; the security page lists the compliance milestones that gate the bigger-buyers, and everything else gets weighed against those.
If something on this page is the reason your district would adopt Fundly sooner, tell us — it goes onto the working list, and the list gets revisited at every planning round.