TΛSΛWOM
Services
About
Projects
Blog
© 2026 TΛSΛWOM. All rights reserved.
Book a Callinfo@tasawom.com
Boutros Tawaifi

Boutros Tawaifi

Founder & Lead Engineer, Tasawom

Cairo, Egypt

I'm Boutros Tawaifi, full-stack engineer and founder of Tasawom. Since 2021 I've been lead engineer for Orbit Sports Data, building and operating the technical infrastructure behind their live sports data platform: reporter tools used courtside, low-latency event ingestion and delivery APIs, the admin platform, and the AWS infrastructure underneath it. When an analyst reports a goal, that event moves through systems I built to a paying client's platform in under 200 milliseconds. Downtime during a live match is not an option. I'm still Orbit's lead engineer today, and that engagement now runs through Tasawom.

That work taught me something specific about operational software: the gap between code that works and a system a team can actually run is where most projects fail. Documentation nobody reads. Handoffs that leave the client dependent on the original developer. Tools built for the demo, not for daily use.

Tasawom exists to bring that same engineering standard to other businesses running critical workflows through manual coordination: reliability, operational clarity, and systems your team owns after launch. I co-founded Tasawom with my brother Yousef, who runs company operations and logistics. I lead every engagement personally. You work with the engineer building your system, not an account manager describing it.

What I Build

  • Internal operational platforms
  • Automation and AI workflow layers
  • Role-based dashboards and admin tools
  • Multi-role business systems
  • Custom software replacing spreadsheet-heavy operations

The common thread: replacing fragmented manual coordination with systems your team can operate and own without calling me back.

How I Work

  • Direct involvement on every engagement. You work with the engineer building the system, not an account manager describing it.
  • Work starts with the workflow. If the process is not understood first, code only makes the mess move faster.
  • Scope, timeline, and acceptance criteria are defined before a build expands.
  • Every system ships with documentation and operating context — not as a black box your team has to reverse-engineer after launch.

Start a Conversation

If your team is running critical work through manual steps, disconnected tools, or processes that depend on someone remembering the next step, describe the workflow. We'll tell you what a system for it looks like.

Book a Free Workflow Teardown