What We Learned Spinning Out a Project (From Hive to Sentient Futures)
By SofiaBalderson @ 2026-01-20T19:28 (+14)
TL;DR: Last year, we spun out Sentient Futures (previously incubated within Hive under the name AI for Animals). The process was ultimately successful and gave both teams more clarity and autonomy, but it took significantly more time and operational effort than we anticipated.
Acknowledgements: Many thanks to Kevin Xia and Constance Li for providing valuable feedback and additions to this post.
Introduction:
Sentient Futures began as a programme within Hive (initially under the name AI for Animals), and we spun it out as an independent legal entity about 1.5 years later as its focus became more distinct.
A few people have asked about this experience, so I decided to write it up, especially because I found surprisingly few practical resources on the topic. We’re sharing what worked for us (and what we underestimated) in case it helps others reduce friction and confusion during a spinout. This isn’t a universal playbook, and every spinout is different, but I hope it’s a useful reference.
Who this post is for:
This is mainly aimed at leaders of small organisations, incubators, and fiscal sponsors who are considering whether (and how) to separate a growing programme into an independent entity. It’s most relevant for sponsors where fiscal sponsorship is a supporting function rather than a core programme or primary area of focus.
A note on “stages” of separation
One helpful way to think about a spinout is as a series of separations rather than a single moment. In our experience, the process often moves through stages:
- Front-facing identity: clarifying branding and communications so external stakeholders understand the relationship (and the change).
- Front-facing tech: separating things like websites and community spaces (e.g., Slack workspaces) so the public-facing footprint matches the new reality.
- Operational infrastructure: moving financial and admin systems (e.g., bank accounts, bookkeeping, insurance, and tools like Google Workspace and email) so day-to-day operations are truly independent.
Only once you’re confident the separation is real and you’re ready to commit does it usually make sense to pursue full legal independence (e.g., applying for 501(c)(3) status, for US-based nonprofits). At that point, it’s important to plan for higher operating costs, since the new entity becomes responsible for its own governance and compliance (bookkeeping, compliance, board, insurance, etc.), and to ensure it has dedicated funds to cover that runway. If the project's team isn't sure if incorporating is the right step for them, but they can't stay within the current entity, they can consider finding another fiscal sponsor (see some common fiscal sponsors in the movement here).
1) Timing and Decision-Making: Spin out sooner than you think
One of our biggest takeaways is to start the process as soon as it becomes clear the project’s focus is meaningfully different from the parent org. For us, once the spinout was officially complete (Sentient Futures became fully independent), Hive found it much easier to stay focused on its core mission. Delaying increases the “debt” of shared systems: as a project grows, separation becomes harder, slower, and more expensive. If you are already debating whether it’s time, it probably is. There are exceptions, but if the project is clearly diverging in mission and stakeholder expectations, earlier separation is usually cheaper and cleaner.
The hardest part: deciding (and having the conversation)
If I had to name the hardest part, it was simply deciding and having the conversation. The spinout itself is mostly a project plan once you’re committed, but reaching commitment can take longer than expected because it’s emotionally loaded: you’re balancing responsibility, attachment, brand clarity, and how it will land with stakeholders.
What helped us was pressure-testing the two main paths with people who’d seen both outcomes: spinouts and long-term fiscal sponsorship. We initially leaned toward keeping Sentient Futures as a programme under Hive long-term, but we consistently heard from experienced operations professionals that for a small charity, long-term fiscal sponsorship can become heavier than expected. It’s operationally heavy, hard to govern cleanly, and can create persistent ambiguity around ownership, accountability, and strategy. The longer the program stays part of your charity, the harder it becomes to spin out.
That made the trade-off much clearer. For the conversation itself, it helped to anchor on shared intent (“we want both Hive and the spinout to thrive”), state the decision plainly, and then move quickly into practical next steps with a timeline so it felt like a confident transition plan rather than an open-ended debate.
What made the process smoother
After the call, we created a shared transition plan document and an Asana project with tasks, owners, and deadlines, which helped us stay organised.
We also benefited a lot from having operations professionals supporting both Hive and Sentient Futures throughout the process, and we’d strongly recommend that where possible (see this list of operations professionals in animal advocacy the movement).
Timeline note
From making the decision to the spinout being fully official, our process took ~9 months. I don’t think it needs to take that long. We intentionally moved at a pace that gave Sentient Futures plenty of time to set things up without making the transition stressful for anyone. In many cases, I think you could do this in ~3–5 months, especially if the new entity already has (or quickly obtains) its nonprofit status and can move faster on banking, tools, and contracts.
If you have the luxury to choose when to spin out, it may make sense to start operational incorporation at the beginning of the year, then you will have one fewer year of paperwork to submit (at least in the US).
- Month 0: Decision + alignment conversation
- Month 1: Transition plan + comms plan + stakeholder heads-up
- Months 1–3: Tool/account separation + banking + applying for non-profit status
- Months 2–4: Website/branding updates + public announcement
- Months 3–5: Clean-up, handover, permissions, final regrant/payment reconciliation
2) The Identity “Grey Zone”
Even if your team understands the split, the community (and funders) often lag behind. We encountered several instances of “blurriness,” and it mattered more than we expected.
Common failure modes:
- Funding confusion: Some funders understandably weren’t sure whether Hive and Sentient Futures were the same organisation, which can complicate partnerships and funding pathways.
- Hiring missteps: Before we decided to spin Sentient Futures out, we used “come work with us” language for Sentient Futures hiring that was branded like Hive, which inadvertently deepened confusion.
- Visual persistence: Because founders are often highly visible, people may not realise they are no longer operationally involved in the parent org.
Clear visual and verbal cues
We learned that small tweaks go a long way in reinforcing separate identities:
- Apparel: Even before the official spinout, we prioritised wearing the specific org’s shirts at events to reduce visual confusion.
- Digital presence: We recommended that leadership update Slack titles and LinkedIn roles (e.g., “Founder, Sentient Futures | Board Member, Hive”) to foreground the new role.
- Website language: We moved the Hive reference out of the first sentence of Sentient Futures’ “About” page and updated the Hive website to refer to Sentient Futures as an independent organisation rather than a programme.
3) The Back Office Ops: it takes longer than expected
Operational separation was time-consuming, especially for the Sentient Futures team. Our default approach was to separate all accounts unless a resource could be replicated easily without a meaningful downside.
Key hurdles included:
- Fiscal sponsorship: We used a direct-project fiscal sponsorship structure initially (Model A; you can read more about fiscal sponsorships here), and later shifted to a regranting-style arrangement while the new entity worked toward its own 501(c)(3) status.
- Tool migration: Moving off shared Google Workspace, Asana, 1Password, and Airtable requires significant admin time.
- Nonprofit discounts: Re-applying for TechSoup and Google for Nonprofits often requires documentation (and sometimes waiting for determination/verification), which can slow down the transition. For example, in the US, the IRS can take up to 1-2 months to add you to their public registry, which is required for some of the discounts.
- Bank accounts: Setting up separate banking accounts and transitioning payments should be prioritised early. It can take time, especially when calculating the final amount of the regrant if applicable.
4) Spinout doesn’t mean cutting ties
We’ve maintained ongoing mentorship and a few shared channels so the new team can still learn from Hive’s processes during the transition. Constance (ED of Sentient Futures) remains a Hive board member, and she’s still part of channels where there’s overlap and mutual learning. If you have the Premium (and above) Slack space subscription, you can set up Slack Connect to enable all members to chat from their own Slack spaces without having to switch.
If you have capacity, we recommend creating an “Alumni Channel” where the new org can ask questions of your operations or leadership teams, at least until their own ops function is fully up and running.
Appendix: Spinout Checklist (non-exhaustive)
1) Strategic and legal transition (check out this great post on how to set up a 501c3 quickly)
- Define sponsorship model: Use a direct-project structure initially, then shift to regranting-style arrangements as needed while independent tax status is secured
- Entity and tax status: Apply for independent IRS tax-exempt status
- Banking and funds: Open a separate bank account (e.g., Mercury) and transfer project-specific funds from the parent organisation
- Formal notification: Once tax-exempt status is received, formally notify the parent organisation to update legal and fiscal records
2) Digital infrastructure (the “backend”)
- Google Workspace: Create a new workspace, migrate files, and set up independent email aliases
- Project management: Request support from Asana/Tally/Canva to move projects/designs between accounts (if possible)
- Password security: Establish a separate password-sharing infrastructure (e.g., 1Password) account and migrate credentials
- Access hygiene: Remove spinout team access from parent org platforms where appropriate
- Database and CRM: Create independent CRM/databases and move relevant stakeholder data
- Shared resource clarity: If still sharing team time/resources, establish a transparent system for prioritisation across separate workspaces
3) Communications and branding
- Website content: Remove parent org references from the first sentence of the “About” page and reframe the parent as an “incubator” (if that’s accurate)
- Footer transparency: Use specific language such as “fiscally sponsored by [X]” until tax status is finalised
- Email tool migration: Change publication ownership and subdomains while ensuring existing links remain functional
- Social and video: Migrate YouTube videos/playlists to a new channel (may require download + re-upload)
- Branding audit: Check public pages, Slack channels, and public resources to ensure language doesn’t imply the project is still an internal programme
4) Community and visual identity
- Title hierarchy: Update Slack and LinkedIn profiles to foreground the new role (e.g., “Founder, Sentient Futures | Board Member, Hive”)
- Profile neutrality: Change photos/backgrounds to avoid visual “blurriness”
- Apparel protocol: Wear organisation-specific shirts at conferences to reduce confusion
- Launch plan: Decide how to launch (e.g. LinkedIn post(s), a launch party, a one-off event, an email announcement, etc.)
5) Software and billing
- Nonprofit discounts: Re-apply for non-profit discounts for the new entity (requires IRS determination letter or equivalent, some discounts such as Goodstack and Techsoup will require you to be on the IRS registry, which takes longer)
- Billing audit: Create new accounts for the tools you need. Move any relevant project subscriptions from the parent’s card to the new organisation’s card. For smaller, less-used tools (e.g., Bitly), decide whether separate free-tier accounts are sufficient.