IROPO Business Plan
International Registry of Pet Offenders (IROPO)
This document is a living plan for turning IROPO from a research/prototype repository into a sustainably funded, publicly useful registry. It should be revisited and updated as the project matures — treat it as a companion to the roadmap in README.md, not a replacement for it.
1. Executive summary
IROPO is a nonprofit-oriented animal-welfare project that aggregates public and official records into a single, verifiable source of truth documenting people who have harmed animals, and publishes that information at iropo.org for advocates, shelters, rescues, adoption agencies, and the public.
The project is currently a data-collection and research effort with no revenue, no formal legal entity, and no dedicated funding. This plan defines what IROPO will offer, how it will be built and operated, and — most centrally — how it will be funded, since funding is the current blocker called out in the README’s “Mission and goals” and “Roadmap” sections.
2. Mission and vision
- Mission: Give the public and animal-welfare community a reliable, well-sourced registry of animal-cruelty offenders to support accountability, safer adoptions, and informed advocacy.
- Vision: Become the standard reference that shelters, rescues, journalists, and policymakers check before making decisions related to animal welfare and animal-cruelty offenders.
- Values: accuracy and provenance over speed; public/official sourcing only; a clear correction and dispute process; privacy- and legal-risk awareness (see README “Legal & ethical considerations”).
3. What the business will offer
3.1 Core offering (free, public good)
- A searchable public registry at
iropo.org of animal-cruelty offender records, each with source citations, verification status, and a correction/removal path.
- State/city coverage starting with the states already represented in this repository (NC, ND, NY), expanding over time.
3.2 Supporting offerings (to help fund the core mission)
- Verified data access / API tier — a rate-limited or licensed API for shelters, rescues, background-check vendors, and researchers who want structured, machine-readable access beyond the public search UI.
- Institutional partnerships — data-sharing or referral agreements with animal-welfare organizations, humane societies, and adoption platforms that want to screen applicants against the registry.
- Grants-funded research reports — periodic public reports/dashboards on animal-cruelty trends by state, useful to press and policymakers, tied to grant deliverables.
- Merchandise / branded donations page — low-effort, low-priority revenue support (stickers, apparel) tied to the mission, mainly for community engagement rather than material funding.
The core registry must remain free and public; paid tiers apply only to bulk/API/institutional access, not to basic public search.
4. Market and users
- Primary users: individual members of the public, animal-welfare advocates.
- Institutional users: animal shelters, rescues, and adoption agencies performing applicant screening; journalists and researchers; policymakers evaluating animal-cruelty enforcement.
- Why now: data already exists (FBI NIBRS, state/local agency records) but is fragmented across incompatible formats and systems; no consolidated, provenance-tracked public registry currently exists.
5. Legal and organizational structure
Before any funding or public launch, IROPO needs a formal legal footing:
- Evaluate forming a 501(c)(3) nonprofit (or fiscal sponsorship under an existing nonprofit) to enable tax-deductible donations and grant eligibility. Fiscal sponsorship is the faster near-term path while full nonprofit status is pursued.
- Obtain legal review specific to publishing personally identifying information about individuals (defamation, privacy, and jurisdiction-specific risk), as flagged in the README’s legal & ethical considerations.
- Define governance: who has authority to add/remove/correct records, and an appeals process for disputed entries.
- Confirm licensing terms for any third-party data sources (e.g., FBI Crime Data API terms of use).
6. Implementation plan
This maps directly onto the existing README roadmap, sequenced into phases with funding gates.
Phase 0 — Foundation (pre-funding)
- Formalize legal structure (fiscal sponsorship or nonprofit filing).
- Define the canonical offender/case record schema (fields, identifiers, source references, dates).
- Draft data governance, verification, and correction/dispute policies.
Phase 1 — Data aggregation (current focus)
- Catalog and evaluate data sources (FBI NIBRS, state/local agency records, public court records).
- Build a US city/state coverage matrix.
- Build scrapers/importers for the states already represented (NC, ND, NY), then expand.
- Stand up a verification workflow and a single source-of-truth datastore with provenance tracking.
- Choose the framework/deployment model (static/GitHub Pages vs. database-backed application) based on data volume and query needs identified in Phase 1.
- Build the ingestion pipeline, storage model, and update cadence.
- Build the public browse/search interface with citations, verification status, and correction affordances.
- Add accessibility, responsive design, and basic SEO.
Phase 3 — Launch and growth
- Set up analytics, contact paths, and feedback mechanisms.
- Launch institutional/API access tier for shelters, rescues, and partners.
- Promote across social media and animal-welfare communities.
- Establish an ongoing maintenance plan (updates, reviews, corrections, archival).
Each phase should only begin once the funding needed to staff and run it (Section 7) is secured or credibly committed — avoid scaling data collection or publishing faster than verification and legal review can keep up.
7. Funding plan
7.1 What funding is needed for
- Hosting and infrastructure: database hosting, storage for source documents, API infrastructure.
- Tooling: scraping/automation tooling, monitoring, backup.
- Legal review: attorney time for privacy/defamation review and nonprofit filing.
- People: part-time or contract help for data verification, engineering, and design once volunteer capacity is insufficient.
- Promotion: basic outreach/design costs for launch materials.
7.2 How to raise it
- Grants: apply to animal-welfare foundations and philanthropic grant programs (e.g., ASPCA, Petco Love, Bissell Pet Foundation, and similar organizations that fund animal-welfare data/advocacy work) once fiscal sponsorship or nonprofit status is in place.
- Individual donations: a donation page on
iropo.org (via a payment processor or the fiscal sponsor’s donation infrastructure) once the site has a public presence worth donating to.
- Crowdfunding campaign: a time-boxed campaign (e.g., GoFundMe, Kickstarter-style for nonprofits) to fund a specific milestone, such as “launch the public beta for three states.”
- Corporate/partner sponsorship: pet-industry companies, shelters, and rescues that benefit from the registry may sponsor hosting or API costs in exchange for recognition or early access.
- In-kind support: apply for nonprofit hosting credits/grants (e.g., cloud provider nonprofit programs) and pro-bono legal clinics to reduce cash funding needs before cash funding exists.
- Volunteer labor: treat contributor time as the primary “funding” source during Phase 0–1, reserving cash fundraising for Phase 2–3 costs that cannot be met by volunteers (hosting, legal, verification review).
7.3 Sequencing
- Secure fiscal sponsorship or file nonprofit paperwork (unlocks donation/grant eligibility).
- Launch a simple donation page and a small crowdfunding campaign tied to a concrete milestone (e.g., “complete verified NC/ND/NY data” or “launch public beta”).
- Use early funding to cover hosting/legal costs and any contract help needed for Phase 2.
- Apply for larger foundation grants once there is a working public beta to point to as evidence of traction.
- Pursue institutional/API partnerships as a recurring revenue stream once the registry has enough verified coverage to be useful to shelters and rescues.
8. Operating budget (illustrative, to be refined)
| Category |
Phase 0–1 (pre-launch) |
Phase 2–3 (post-launch, annual) |
| Hosting/infrastructure |
Low (static/GitHub Pages, free tiers) |
Moderate (database hosting, API) |
| Legal review |
One-time (nonprofit filing + privacy review) |
Occasional (dispute/removal cases) |
| Contract/part-time help |
Minimal, volunteer-driven |
As funding allows, for verification and engineering |
| Promotion |
Minimal |
Modest (launch campaign, ongoing outreach) |
Exact figures depend on hosting choices and legal counsel quotes; this table should be replaced with real numbers once those quotes are obtained.
9. Risks
- Legal/reputational risk: publishing information about identifiable individuals carries defamation and privacy risk if sourcing or verification is weak — mitigate with strict public/official sourcing, provenance tracking, and a working correction/removal process before any public launch.
- Funding risk: without a legal entity, donations and grants are not readily available — prioritize Section 5 and 7.3 step 1 early.
- Volunteer sustainability risk: as a volunteer-driven project, progress depends on contributor availability — track this openly in
CONTRIBUTING.md and roadmap issues.
- Data quality risk: inconsistent or incomplete source data could undermine trust — verification workflow (Phase 1) must be in place before Phase 2 launch.
10. Next steps