BlindspotLab (@BlindspotLab) header
BlindspotLab (@BlindspotLab) profile picture

We help founders turn rough ideas into live products. AI-native strategy, design, engineering and automation. Built by @MojeebMotion.

Joined October 2024
Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)Photo by BlindspotLab (@BlindspotLab)
Dear BSL family, we've a new home. We've been thinking about giving BlindspotLab a new home since Sept 14th, when we incorporated our company with CAC. But due to some circumstances, our founder got busy with a client project, fell sick, and the doctor said he had to rest because he had been working without enough rest. That's what caused the delay in the new BlindspotLab design. But here it is now. Restructured, redesigned, and on a new host. Cheers to new beginnings! BlindspotLab, 25/09/2026
hello everyone, we’re migrating from our former host that’s vercel to cloudflare, and our website will not be online for some minutes. thank you BlindspotLab 21/09/2026
1
1
3
301
BlindspotLab retweeted
“Football belongs to the fans.” After Ronaldo’s 2008 Ballon d’Or topped the fan vote, I built THE GOLDEN RUN ⚽🏆 a free football game inspired by his road to 1,000 goals. Score. Compete. Climb the rankings. Chase 1,000. Play: goldenrun.fun
Football belongs to the fans! Thank you to all the fans around the world, the Ballon D’Or of All Time is also yours.
1
1
2
82
BlindspotLab retweeted
Ronaldo or you? Who's going to hit the first 1000 goals? goldenrun.fun
Football belongs to the fans! Thank you to all the fans around the world, the Ballon D’Or of All Time is also yours.
1
1
78
Please help vote for our founder. Thank you as you do so.
1
88
We rebuilt BlindspotAgents into something much more serious. Meet PULSE by BlindspotLab. The first version was useful, but it was still too manual. One command at a time, Notion acting as runtime state, one AI provider, and no real system learning from outcomes. PULSE changes that. It now runs with: • 10 scheduled jobs • 8 agent roles • NVIDIA as primary AI provider • automatic provider fallback • Cloudflare D1 as operational state • GitHub, search, RSS, Hacker News, Devpost and Telegram as inputs • human approval before anything reaches an audience • 289 automated tests passing The biggest lesson from rebuilding it was simple: AI should not always replace the person. It should remove the friction around the person. That is how we now think about automation at BlindspotLab too. A lot of teams do not need “an AI product” for the sake of saying they use AI. They need someone to look at the repetitive parts of their day-to-day work and ask: What should software handle automatically, and what should still require human judgment? If your team still spends too much time on repetitive research, reporting, internal workflows, follow-ups, operations, content preparation, product tasks or manual coordination, there is probably a better system hiding inside that process. We help founders and teams map those workflows, automate the right parts, and turn them into reliable systems. DM us for an AI workflow / automation consultation. From rough idea to live product.
2
1
4
336
Good products deserve to be discovered. @Arcapush, one of our studio products, has a new look and a new milestone: 300+ products indexed. What’s new: • Arcapush Web v0.4.0 • Arcapush CLI v0.2.4 • MCP integration for AI agents • A refreshed design system • A clearer focus on discovery and distribution Discover products, AI agents, and hackathon builds worth your attention. Building something? Give it a place to be found. Explore or submit for free → arcapush.com
2
2
2
562
Introducing Blindspot Thesis. First up: a teardown of @usevano_'s website, covering its hero, page flow, CTAs, SEO and AEO. Need help finding your product’s blind spots and deciding what to improve? DM us or email [email protected] to book a consultation.
Since Vano launched, I’ve wanted to take a proper look at its website. I finally made time for it and turned the review into the first Blindspot Thesis. A website teardown covering: • Hero and value proposition • Section flow and messaging • CTAs and the path to taking action • SEO and AEO I looked at where the experience falls short, what needs improving, and how I’d approach those changes, with visual examples to make the recommendations clearer. The goal is simple: help visitors understand the product, see its value, and know what to do next. Read the first Blindspot Thesis: blindspotlab.xyz/thesis/vano Building a product and need a fresh pair of eyes? I work with founders through BlindspotLab to uncover blind spots, identify what needs adjusting, and prioritise what to work on next. DM me or email [email protected] to book a consultation.
1
1
3
172
Nigeria at 66 🇳🇬 Celebrating the people building, creating, and making things work. From all of us at BlindspotLab, Happy Independence Day.
🤖 Made with AI
1
3
187
A new look. The same drive to build.
🤖 Made with AI
1
3
263
BlindspotLab retweeted
BlindspotLab get a new home, and i want to share with you everything i worked on layer by layer. the first is the Hero, redesigned with new BlindspotLab wordmark, new H1, six ambient icons, and new content for the hero.
Dear BSL family, we've a new home. We've been thinking about giving BlindspotLab a new home since Sept 14th, when we incorporated our company with CAC. But due to some circumstances, our founder got busy with a client project, fell sick, and the doctor said he had to rest because he had been working without enough rest. That's what caused the delay in the new BlindspotLab design. But here it is now. Restructured, redesigned, and on a new host. Cheers to new beginnings! BlindspotLab, 25/09/2026
3
1
4
193
hello everyone, we’re migrating from our former host that’s vercel to cloudflare, and our website will not be online for some minutes. thank you BlindspotLab 21/09/2026
2
3
359
BlindspotLab retweeted
i think i can finally write about this. aitax.fun was my first paid client build as a developer. i met the project as a rough idea. no finished architecture. no complete game. just the direction of what the founder wanted to build. my job was to turn it into something that actually worked end to end. the product became a PVP Bitcoin UP/DOWN game on Robinhood Chain. so I built the frontend, smart contracts, the chainlink data streams integration, round automation, settlement, claims, refunds, Burn Accumulator, admin dashboard, health monitoring, indexing, wallet flows, production deployment, all connected together, and working end to end. but getting there was not smooth. one of the hardest moments came after we went live and rounds kept refunding instead of settling. at first, it looked like an oracle or RPC availability problem. it wasn't. i kept digging. the oracle's priceAt(boundary) function was correctly reverting with ReportUnavailable() when the required historical BTC boundary had not been stored yet. that revert was supposed to tell our coordinator: "fetch the authenticated chainlink historical report, submit it, then continue settlement." but our custom RPC transport was swallowing the EVM revert data. instead of seeing the exact ReportUnavailable() signal, the coordinator saw a generic RpcRequestError. so it treated the situation like an RPC failure. the chainlink report retrieval path never ran. and the round eventually reached its refund deadline. we watched multiple rounds refund. that part hurt. this was mainnet. people were using something I built. every failed settlement felt very different from a failing local test. i was tired, at some point, i was genuinely scared that I had built something that wasn't going to work reliably. but I kept tracing it: - revert bytes - RPC responses - oracle boundaries - coordinator state - retry timing - transaction receipts Until the actual failure became obvious: i fixed the transport to preserve EVM revert data. i matched the exact oracle failure condition instead of treating every failure the same. i changed failed settlement retries from the old long delay to a much faster recovery path. i added stage-aware error reporting. i hardened transaction persistence and recovery. then the lifecycle started doing what it was designed to do: entry → lock → oracle → settlement → claim → burn. that experience changed how I think about building production systems. a successful build is not when the UI looks finished, it is not when the contract compiles, it is not even when everything passes locally, it is when the full system survives reality. - networks fail, - providers time out, - transactions get weird, - external services behave differently from mocks, the important part is whether you can understand the system deeply enough to find the real failure instead of patching the symptom. i also built the operational side so the owner doesn't need to live inside Blockscout. contract parameters can be managed from the admin frontend with the owner wallet. settlement is automated. lifecycle functions remain permissionless. the BurnAccumulator is visible to everyone, and once its threshold is reached, anyone can trigger the burn. the contracts remain the source of truth. this started as my first client gig. there were moments I was tired. moments I was scared. moments I wondered whether i had taken on too much. but i learned more from shipping this system than I would have learned from another ten unfinished side projects. i met AITAX as an idea. now it is a working product. and after all those rounds that refused to settle... we're finally UP. 🚀
We met AITAX as a rough idea. Today, it is a working end-to-end product on Robinhood Chain. The original idea was simple: Build a PVP prediction game where players use $AITAX to predict whether Bitcoin moves UP or DOWN. Turning that idea into something people could actually use required much more than building a game screen. 👇🧵
6
4
1
13
920
We met AITAX as a rough idea. Today, it is a working end-to-end product on Robinhood Chain. The original idea was simple: Build a PVP prediction game where players use $AITAX to predict whether Bitcoin moves UP or DOWN. Turning that idea into something people could actually use required much more than building a game screen. 👇🧵
AITAX.fun is LIVE. Predict where the market moves, climb the leaderboard, and prove your calls. 🏆 Top 5 over the next 3 days win 100 USDT each. Make your prediction. Take the top spot.
1
3
1
5
929
That is what we wanted to build with AITAX. Not just another interface around a token. A complete product where the user-facing experience, contract architecture, automation and operational infrastructure all work together. There are still important trust boundaries we intentionally make visible. The owner retains control over certain future-round parameters. Those changes require the owner wallet and happen onchain. A round that has already opened keeps the parameters it started with. The team cannot manually select a winner through the game contract. The frontend cannot override settlement. The chart is not the oracle. And protocol state can be verified independently onchain. That transparency matters to us. We are not interested in hiding complexity behind the word "Web3." Our job is to absorb the complexity, engineer the system properly and expose the parts users actually need to understand. -/12
1
1
39
AITAX came to BlindspotLab as a rough idea: we helped turn it into working product user use. If you're founder, you have the rough ideas, and you want to execute it, you can always work with us to build your dream products for you.
1
27