SIFT – How we work
From an idea to a live change · Cannaball Ads × BIX Tech · November 17, 2026
Lucas Menegazzo · Delivery Manager · BIX Tech
Three things that affect you.
One shared board
Everything we're working on lives on one board. You can check the status of any item at any time, without having to ask.
Three environments
Changes are built and tested away from your live traffic. Only approved work reaches Production.
Your approval
Nothing new goes live until the person you name on your side has seen it and said yes.
Three versions of SIFT, one job each.
Development
Where active coding happens. Work here is unfinished and can break, and that's expected.
to test
Staging
Where we test changes before release. A copy of Production, so we can show you a change exactly as it will work.
by you
Production
The finalized, approved live version. Your networks and their real clicks run here.
How a change reaches Production.
Request
You or we add it to the board: a new feature, a bug, a change of plan.
Prioritize
On the weekly call, you decide what comes next. We tell you the size and the trade-offs.
Build and test
Cácio builds it in Development and tests it in Staging.
Review and approve
We show it to you in Staging. You approve it, or ask for changes.
Release
We publish it to Production in an agreed window and send you a short note on what changed.
Who does what.
Your side
- Set the priorities on the weekly call
- Name one person who approves releases
- Review changes when we demo them
- Tell us when something looks wrong
BIX side
- Write, test and release the code
- Keep the board up to date, every day
- Send a short note with every release
- Watch Production and fix issues first
Your window
into the work.
One board that shows what we're doing,
what's next and what's done.
Five columns, left to right.
Example cards. The board link opens the same view.
What's on a card.
- Title
What will change, in plain words. - Status
Which column it's in. - Milestone
Which delivery date it belongs to. - Priority
P0 blocks the current milestone, P1 is needed for it, P2 is nice to have. - Size
Rough effort, from XS (a few hours) to XL (too big, so we split it). - Labels
Which part of the product it touches.
Milestones are the delivery dates.
The plan from the kickoff. On the board, each one shows how much is done.
Assessment
Access, tracker test, architecture and readout.
Fraud detection with IPQS
Better accuracy, fewer false positives.
Productization and first tracker
From Base44 to a real product.
Infrastructure and latency
Cut the 1–3 s redirect.
Launch support
Live traffic, fixes and tuning.
When changes go live.
A fixed release window
Tuesday to Thursday, within 7 AM–4 PM ET, when we're all online. Never on a Friday or right before a holiday.
A short note every time
What changed, what to check, and anything you may need to tell your networks.
Undo in minutes
If something looks wrong after a release, we switch back to the previous version first and investigate after.
Urgent fixes
A fix for something broken in Production can go out outside the window. We'll tell you before it does.
Found a problem? Here's what helps.
Send us, in the channel
- What you were doing
- What you expected, and what happened
- Network, campaign or link involved
- When it happened (ET)
- A screenshot, if you have one
Live clicks failing or blocked wrongly
We stop other work and fix it, or roll back.
Something broken, with a workaround
It goes to the top of the board.
A small issue or a new idea
It goes to the backlog, and you prioritize it.
Questions you may have.
Will a release interrupt our traffic?
No planned downtime. A release switches over in seconds, and we can undo it right away.
Can we change priorities mid-stage?
Yes. Tell us, and we'll show you what moves out to make room.
Do we need to learn GitHub?
No. A link to the board is enough to follow along. Comments are welcome, never required.
Can we see work in progress?
Yes. We demo in Staging before anything goes live, and you can ask for a demo anytime.
What happens to the Base44 prototype?
It keeps running as it does today until the new version is approved. We'll plan the switch with you.
What if a date slips?
You'll see it on the board first, with the reason and the new date on the weekly call.
To agree today.
Thank you.
Questions?
Lucas Menegazzo · lucas.menegazzo@bix-tech.com