Hoodoo Ventures · operating system plus marketing

Ready yourcompany forsuperintelligence.

We install Jackalope, one operating system for the whole company. Then we run world-class marketing on top of it. It runs Pickleball Inc and the PPA Tour today.

  • OperateOne record. Agents do the work.
  • MarketSearch, sites and campaigns
  • ProveEvery dollar to its source
Event recordPPA-ATL-GA

PPA Atlanta

Sample event · illustrative numbers

$1,240,000.00

  • Tickets soldTixr · 3,800
  • Sponsor paidInvoice · 150,000.00
  • Travel booked40 of 46 · flights and rooms
  • Cards coded automatically212 of 212 · in 6 seconds
Event P&L · live09:00 MT

$286,000.00

Net to date · posted before anyone asks

Jackalope in production

Pickleball Inc · PPA Tour · as of Oct 2026

137

events on one record, every dollar joined by event code

16 of 17

Tixr payouts tie to the books to the penny

1.1M

customers deduped to one ID each

52

scheduled agent jobs a day, each one logged

About 200 staff · 4 brands · 245 API endpoints · 2,600+ commits · built in 4.5 monthsusejackalope.com

The problem

Five jobs eat yourteam's week.

We run them on one record. The people you hired for the real work get to do it.

JobWhat it looks like todayWho does it now
01Booking travel and chasing receiptsFlights, hotels, per diem, card matchingHandled by Hoodoo + Jackalope
02Closing the books for every eventOne P&L per event, live before it endsHandled by Hoodoo + Jackalope
03Running campaigns and proving they workedEvery send, open and click against sales paceHandled by Hoodoo + Jackalope
04Selling, building decks, reporting to partnersPipeline, decks from call notes, recaps from real numbersHandled by Hoodoo + Jackalope
05Pulling the numbers, againKPIs live, reports drafted for youHandled by Hoodoo + Jackalope
06Putting on great workThe thing your company is actually forBack to you

From ticket to the books

A ticket payout becomesa journal entry. To the penny.

Finance trusts it because it reconciles. Tixr payouts tie to Sage Intacct on 16 of 17 payouts.

Live at the PPA

What happens: Tixr pays out → Jackalope drafts the journal entry on the event code → it ties to the penny, and Finance approves.

Tixr · payout

$84,000.00

PPA Atlanta · ticket sales, net of fees · sample

Sage Intacct · journal entry

$84,000.00

Deferred revenue · PPA-ATL-GA · 0.00 difference

Payout in transit · 1 day

Books sync · 7:45

Sep 2 · 07:45:00 – 07:45:06

Match · 07:45:04

Tied to the penny

Payout, fees and event code → PPA-ATL-GA

Payout · 07:45:00

Tixr payout lands84,000.00 by ACH · sample

Journal · 07:45:06

Entry drafted, waits for approval84,000.00 − 84,000.00 = 0.00

Automatic spend coding

Every swipeknows its event.

Jackalope reads every source a card charge touches. It finds the event, codes the account and matches the receipt by airline ticket number.

Live at the PPA

What happens: a card is swiped → Jackalope wires it to the event and codes it → the receipt attaches itself.

What Jackalope readraw · as received · sample
Divvy · cardtxn 88213 "DELTA AIR 0062381994" amt=486.20
Airline · e-ticketticket 006 2381 99417 dest=ATL dep=10-14
Travel rosterPPA-ATL-GA traveler=ops_lead dates=10-14..10-19
AI coding guessaccount=6110 Travel confidence=0.97
Receipt · inboxreceipt.pdf ticket=0062381994417
Coded recordTXN-88213 · Oct 2, 14:06:11

Matched automatically

5 sources · 5 signals · 6 seconds · 0 manual steps

  • Card charge$486.20 · Divvy
  • Ticket number006 2381 99417
  • EventPPA Atlanta
  • Account coded6110 · Travel
  • ReceiptAttached · matched by ticket
Synced to Sage Intacct · event PPA-ATL-GAAudit trail · 5 sources linked
Also handlesDeadline nudges · Missing receipts · Hotel folios split per person · Flight creditsAnything it can't match goes to one review list.

Company travel

Travel thatbooks itself.

Who's going, how they get there and what it costs, for each event on one screen. The counts show what's still open.

Live at the PPAIn-app flight booking: Built

What happens: a person joins the roster → Jackalope plans the flight, room, ride and card limit → a person books and approves.

Roster

PPA Atlanta 46 travelers

Oct 14–19 · sample

Booked so far

By team

home airport → ATL

Court and ref crew14 people
13 / 14
Broadcast11 people
10 / 11
Operations10 people
8 / 10
Marketing and sales7 people
6 / 7
Leadership4 people
3 / 4

Per diem on autopilot

Card limits rise and fall every hour from the travel roster. Someone flies home early, the limit follows.

Travel · PPA Atlanta

Readiness

updated hourly · sample

PPA-ATL-GA
  • Flights bookedhome airport to venue airport40 / 46
  • Rooms assignedrooming list read from a photo44 / 46
  • Rides proposedfrom booked flights, posted to Slack31
  • Per diem limits setcard limits follow the roster46 / 46
  • Hotel contractread itself · cost forecastdone

Booked

6 travelers still open · nudges sent

40 of 46

What it replaces

Cut the software,keep the work.

A shorter stack, not one more login. Each tool goes when Jackalope does its job. The savings ledger is the only place savings count.

Savings ledgerPPA Tour, 2026

banked · committed · proposed
ToolWhat it didNow in JackalopeStatus
DomoDashboardsTicketing and metricsCancelled
HubSpotCRMSales pipeline, fully importedCancelled
SalesforceCRMSales pipelineGone
KORESponsorshipSponsorshipNever bought
Zapier ticket reportDaily sales email9 am Slack reportGone
Booking platformTrip sales, platform feesOwn checkoutGone
Asana, Miro, MilanoteTasks, boards, org chartProjects, requests, org chartCancelling
DropboxBrand assetsBrand libraryCancelling 13 Nov
StampliAccounts payableAP bill captureAround Dec
KlaviyoEmail and SMSCampaignsWith store move
TeamworksPro player hubPro Player CentralContract to 2028

Could go next, anywhere: Slack updates · Monday, ClickUp · Tableau, Power BI · expense apps · deck tools

Saved at the PPA Tour

$800K+

Saved this year

Software cut plus roles not refilled. Bryce's count, Oct 2026.

Integrations

Your stack,finally connected.

Keep the tools your team already runs. Jackalope reads each one and writes it to one event record.

Tickets and commerce

TixrTickets3,800 · sample
ShopifyStore ordersevent merch
Eventbrite
Ticketmaster
Square

Finance

Sage IntacctGeneral ledgerdaily sync
Divvy / BILLCard spend212 coded
Plaid
Stripe
ADP
JackalopePPA-ATL-GA

PPA Atlanta

  • Tickets3,800 sold
  • Storeorders joined
  • Bookstied · 0.00
  • Card spend212 / 212
  • Ad spendMeta, Google
  • Matched automatically9:00
  • Event P&Llive

Marketing

Ad spendby event codeMeta Ads
Ad spendby event codeGoogle Ads
GA4
Search Console
Customer.io

Work

Morning post#tickets · 9:00Slack
Gmail
Google Sheets

Also: BigCommerce · Klaviyo · SEMrush · YouTube · Apollo · Stampli · Hertz · Google Directory · Meet

It does the work, while everyone sleeps

The model proposes.A person approves.

Will the AI go rogue? No. Every agent drafts. Nothing goes outside the company without a yes. Every change has a name on it.

Agent logTonight Mountain time

52 scheduled jobs · every one logged
TimeJobActor
2:00 amAnalytics roll upyesterday's numbers, every sourceJackalope
3:00 amAudience reportwho bought, and from whereJackalope
5:00 amA second AI audits the firsta different model checks the numbersAuditor
5:30 amIntegrity checktotals tie out, or a person hearsWatchdog
7:00 amBank and card feeds pullPlaid · DivvyFeeds
7:45 amThe books syncSage Intacct · journal entries draftedJackalope
8:00 amTickets and registrations refreshevery event, every channelJackalope
9:00 amTicket report posts to Slack#tickets · pace vs last yearJackalope

Roles

  • FinanceApproves journal entries
  • MarketingApproves sends and ads
  • Event leadsSee their events
  • Everyone17 roles · one login

Approval rule

Nothing external goes out without a person.

Journal entry · PPA-ATL-GA84,000.00
Proposed by JackalopeApproved · Finance
  • Emails land as drafts.draft
  • Ads land paused.paused
Every change logged with actor, time and before and after values.52 jobs a day · all live at the PPA
LiveJournal entries draft themselves

Ticket payouts into the books, tied to the penny.

LiveCard limits move on their own

Per diem follows the travel roster, hour by hour.

LiveThe 9 am report posts itself

With a watchdog that flags it if it doesn't.

LiveDecks build from call notes

And pass an A+ check before anyone sees them.

LiveA second AI checks the numbers

Every night, a different model audits the first.

World-class marketing

Marketing you canmeasure to the dollar.

Jackalope makes the numbers true. Hoodoo makes them grow. Same team, same record, no agency reports built by hand.

02 · Attribution and zero-waste ad spend

Every ad dollar sits next to the sale it made.

We match each click to a booked visit or sale. Each campaign gets a call: keep, test or cut. Money moves from what doesn't sell to what does.

Built · Reeds demoNext at the PPA: order-level matching

What happens: an ad click → a visit or sale within 30 days, matched by phone or email → each campaign gets keep, test or cut.

Live at the PPA today: every send sits on one timeline next to ticket pace, by event code. Order-level ad matching is next. Google Ads waits on Google's developer token.

Campaigns · last 30 dayssample data · Reeds demo
CampaignSpendSalesReturnCall
Google Shopping: Bridal$214$12,48058.3xKeep
Performance Max: Store visits$196$6,21031.7xKeep
Meta: Engagement prospecting$162$4,99930.9xKeep
Google Search: Brand terms$236$3,89016.5xTest
Google Search: Watch brands$388$1,2403.2xTest
Google Search: Competitor names$114$00.0xCut

Attribution: click, then a booked visit or store sale within 30 days, matched to point of sale by phone or email.

03 · Campaigns that run themselves

A 120-day plan. Every send against pace.

BuiltSend timeline live at the PPA

What happens: the plan drafts every send → a reviewer approves → email lands as a draft, the ad lands paused.

04 · Sites that sell

Every page ends in a next step.

  • Breitling concept90 pages · 99 speed
  • Reeds Jewelers conceptring pages · store visits
  • PIVOT rebuildsfour brand sites · one lead inbox
Built

What happens: we rebuild the site around the biggest sale → every form lands in one inbox → Jackalope ties the lead to the sale.

Everything it does

What's done today,and what's next.

Scan it in 30 seconds. Every module is a view on the same record, with one login and 17 roles.

LiveIn daily use at Pickleball IncBuiltShipped, light useNextOn the roadmap

Home and daily work

  • My Daymetrics, receipts due, next trip, to-dosLive
  • The Feedmorning recap posts itselfLive
  • Search everythingany module, any personLive
  • Company calendarflights, sends, contract endsLive
  • Phone appinstallable, with pushBuilt

Finance

  • Event P&Lbudget, projected, actual, per eventLive
  • Ticket payout to journal entrydrafts itself, ties to the pennyLive
  • Card spend codingauto-coded, receipts matchedLive
  • Savings ledgerbanked, committed, proposedLive
  • AP bill capturereads PDFs, codes to the eventBuilt
  • Month-end close boardchargebacks, Stripe to the booksNext

Travel

  • Event travel workspaceroster and readiness per personLive
  • Hotels and roomingcontracts read themselves, lists from a photoLive
  • Per diem autopilotcard limits follow the rosterLive
  • Ground plan and foliosrides from flights, bills splitLive
  • Flight booking in the appbook from the rosterBuilt
  • Travel inbox that answerstravelers email, it answersNext

Marketing

  • Marketing hubgoals per event for tickets and budgetLive
  • Meta and Google Adsspend, return, new ads land pausedLive
  • Brand librarylogos, photos, brand booksLive
  • Nightly social graphicsreplaced manual design workLive
  • Campaign buildercadence, channel, audience, approvalBuilt
  • Push to channelsemail as draft, ad as pausedBuilt

Sales and sponsorship

  • CRM pipelineforecast, rep boards; HubSpot importedLive
  • Deal sheets and rate cardpriced assets, approval ladderLive
  • Contracts and renewalsevery signed deal, 180 to 30 days outLive
  • Outbound engineresearch, drafts a person sendsLive
  • Deck Builderfrom call notes, with an A+ checkLive
  • Sales inbox to CRMreads threads, proposes updatesBuilt

Metrics and data

  • Ticketingpace vs last year, projected finishLive
  • Daily Slack ticket reportwith a watchdogLive
  • Customer 3601.1M people on one IDLive
  • Web analytics and SEOevery site, every brandLive
  • Event scorecardseven streams, after each stopBuilt
  • Weekly revenue emaildrafted for leadershipNext

Events and people

  • Events hubone record joins every moduleLive
  • Schedule builderscenarios, promote behind a diffLive
  • Venues93 with specs and site plansLive
  • Directory and org chartfrom ADP; replaced MiroLive
  • Handbook and onboardingsearchable, with policy updatesLive
  • Event creation cascadenew event fires every team's tasksNext

Commerce and talent

  • Store migration centerplan, owners, decisionsLive
  • Catalog and SEO by scriptproducts, redirects, postsLive
  • Order history539K orders backfilledLive
  • Pro player centralprofiles, contracts, obligationsLive
  • Player appbeta in NovemberBuilt
  • Store cutoverJanuary 2027Next

Agents and platform

  • Ask Jackieon every page; reads files, answers, editsLive
  • Agents pageevery job, what it did, what's nextLive
  • Nightly second-model audita different AI checks the numbersLive
  • Roles and sign-in log17 roles, per-person grantsLive
  • Company-wide Jackiesupport AI across brandsNext
  • Instance per companyships before a second companyNext

Why one record

Other tools give you a login.We give you one record.

Most companies run on a dozen tools that each hold a piece of the answer. We put the answer in one place, owned by you.

Hoodoo + JackalopeA dozen tools
Your numbersLive, from the sourceExported and rebuilt weekly
Your receiptsMatched to the card chargeChased by email
Your reportsDrafted for youBuilt by hand on Friday
Your marketingEvery dollar next to the saleClicks in one tool, sales in another
Your dataYours, in one placeRented, in a dozen places

What we learned

What works,and what's hard.

We say the hard parts first, before you find them.

Works

  • One record per event. Every dollar, ticket and flight hangs off one code, so the numbers agree.
  • Live sources, not exports. Pull from the ticketing system, the books and the card feed directly.
  • Drafts, not auto-sends. The system writes it. A person sends it.
  • Build the day you're asked. A problem in the morning, a working screen the next day.

Hard

  • People, not software. Getting a team off tools it knows is the real work.
  • Closed tools. If a vendor won't let the data out, replacing it takes longer.
  • Long contracts. Some tools are replaced but still billed until the term ends.
  • Shaped like an events company. The spine is general, but every proof point today is pickleball.

FAQ

Your questions,covered.

What does Hoodoo do that Jackalope doesn't?

Jackalope is the engine. Hoodoo installs it, runs the marketing on top and stays on the work with you.

Is this only for sports?

No. It was built running a sports company. The spine is general: job, place, client, date. Every proof point today is pickleball, and we say so.

Who owns the data?

You do. Your instance, your data, in one place.

Does AI send things on its own?

No. The model proposes. A person approves. Emails land as drafts. Ads land paused.

Does it replace our tools on day one?

No. It reads them first. Each tool goes when Jackalope does its job, one by one.

Is it ready for a second company?

It runs Pickleball Inc today. A separate instance per company is the next build. It ships before we take on another company.

How fast can we start?

Bring one messy month. See it as one screen the next day.

What does it cost?

It depends on what you want run. Bryce sends a written scope and price after one working session.

Why Hoodoo

Hoodoos are the rockspires of Bryce Canyon.

A hard caprock keeps the soft stone under it standing. That is our job for a company. One hard layer of truth sits on top, so the rest holds.