Nacho Coll

Founder & Principal, X Bot — Blockchain Web Services (BWS)

Updated

I lead the team at Blockchain Web Services (BWS) that builds and operates X Bot — the Telegram bot that turns X (Twitter) activity into leaderboards for crypto communities. My day-to-day spans the whole BWS portfolio; X Bot is one of the products we ship from that same discipline.

Nacho Coll

Background#

I’ve been building on AWS since 2007 — from the very early days of S3 and EC2, long before “cloud” was the default answer. As an AWS Enterprise Architect I designed production-scale systems for top-tier customers including LEGO, Nordea, Vueling, and others in the enterprise Fortune-500 tier. That’s where the operational instincts behind everything I do today were formed: cost discipline, multi-region reliability, and taking observability seriously from day one rather than bolting it on later.

Since 2019 I’ve been focused on two things in parallel: infrastructure for blockchain and decentralized products, and the AI side of software delivery — bringing the same enterprise-architecture discipline to both. That’s the foundation Blockchain Web Services (BWS) runs on today: an AI-native solutions factory with a single operating slogan, Demand Becomes Product. We turn validated market demand into production-ready software — engineered by people, accelerated by AI, accountable end-to-end. Every line of code that ships from BWS is owned by a named engineer.

BWS ships several production products from that same discipline. X Bot is one of them; others include:

  • OpenAgile.AI — engineering discipline for AI-assisted development.
  • Zellbox — CRM for appointment-driven SMBs: customers, bookings, and WhatsApp reminders in one inbox.
  • WallaWhats — real-time WhatsApp alerts when your favorite X/Twitter accounts post.
  • Badges.ninja — blockchain-verified digital badges with a visual designer and REST API.
  • IPFS.NINJA — the simplest IPFS pinning and upload API, with dedicated gateways and a generous free tier.
  • Blockchain Database — a single API to use the blockchain as a data layer.
  • NFT.zK — a straightforward API to mint NFTs without Web3 expertise.

BWS pivoted to being AI-native in mid-2025. AI wasn’t a feature we added — it’s a company we became. The engineering bar didn’t change: what changed is how much research, scaffolding, and testing AI can now carry, so a small team can ship the same shape of production software that used to take a much larger one.

What we work on day-to-day#

My day-to-day spans the whole BWS solutions portfolio — directing roadmaps across the products, reviewing technical design with the team, tightening the AI-assisted delivery workflow that ships all of them, and keeping the engineering discipline consistent from one product to the next. Each product has its own weekly cadence; my job is the connective tissue between them.

For X Bot specifically, we mostly focus on keeping the fetch → score → render → deliver loop accurate and reliable. Areas the team has been hands-on with recently:

  • Data accuracy — X Bot reads from the official X API, so the numbers in a leaderboard match what X itself reports. Keeping that pipeline correct — pulling the right posts for a filter, deduping, and attributing engagement to the right account — is the whole product promise.
  • Scoring + leaderboards — configurable weights for likes, reposts, replies, quotes, and views; a “best tweet of the day” pick; and a rendered leaderboard image posted straight into the Telegram chat on a schedule.
  • Setup that doesn’t lose people — we folded 50+ slash commands into a single guided /setup menu so an admin can pick accounts, cashtags, keywords, and a schedule without reading a manual.
  • Fair, predictable pricing — a FREE plan that covers 100 posts/month with no card, a $19/month PRO plan for 1,000, and ETH credits that never expire — so the cost of tracking a community is transparent and matches usage.
  • Customer support — we handle every ticket directly. Open one in the bot via /setup → ❓ Help & Support and you’ll get a response from a real human — and most days, that human is me.

Articles I’ve written or reviewed#

Most posts on this site carry my byline. Some are drafted by an AI assistant (see the editorial process for the full workflow) and reviewed by me before publication; others are written end-to-end by the team. Either way, every product claim is verified against the live bot before publishing.

A few representative posts:

Browse the blog Editorial process