Make it

Context

Make it is the long-cycle founder-operator chapter: a startup studio and software services company built around turning ideas, customer needs, and internal bets into working software systems.

The company combined venture creation with practical delivery. That meant the work was never only about ideas, code, or sales. It was about creating enough operating capacity to discover opportunities, shape products, serve customers, launch ventures, and keep teams moving across years.

Role

Sanawar founded Make it in 2014 and operated across founder, General Manager, CTO, product, delivery, customer, hiring, and company-system responsibilities. The role required switching between strategy and detail: deciding what to build, structuring teams, managing delivery quality, shaping customer commitments, and creating internal rhythms that could survive pressure.

Constraint

The central constraint was resource allocation under uncertainty. Studio and services work creates competing demands: customer delivery, venture bets, team focus, commercial reality, technical debt, and the temptation to start more than the operating system can absorb.

The work required saying no, sequencing effort, making tradeoffs visible, and keeping momentum without pretending that every experiment deserved equal weight.

What I built and led

The public claims stay deliberately careful: founded in 2014, 15+ ventures launched through the studio model, and 100+ customer initiatives supported. Behind those claims is the operating work of building teams, product direction, engineering delivery, customer systems, leadership cadence, and the judgment to move between service work and venture building.

Make it also created a practical leadership environment: founders, engineers, designers, customers, and operators working through ambiguity rather than waiting for perfect information.

Operating system pattern

The Make it pattern was to convert ambiguity into structured motion:

clarify the opportunity or customer need;
define the smallest useful build path;
assign ownership and delivery rhythm;
use evidence from users, customers, and delivery reality;
decide whether to continue, change, pause, or retire the work.

This is the same operating logic that now translates into AI-native company systems: planning, execution, evidence, review, and continuous improvement.

Evidence and proof

The strongest evidence is duration, breadth, and repeated exposure to real execution: a company founded in 2014, a startup studio and software services model, 15+ ventures launched through the studio model, and 100+ customer initiatives supported.

What this says about the next role

This chapter supports senior leadership roles where the work is not a narrow functional mandate. It is most relevant to GM, COO, VP, Head of, product/engineering leadership, AI operations, and venture-building contexts where strategy only matters if the operating system can execute.

Start a conversation about senior AI, product, operations, or venture-building opportunities.