Twenty-six systems, no client names.

The problem

Work was split between a legacy Tally ERP 9, spreadsheets nobody had standardised, and WhatsApp threads. Vendor invoices took seven to ten days to clear, and three-way matching of purchase orders, goods receipts and invoices carried an estimated 12% clerical error rate.

What was built

• Autonomous ingestion workers capturing vendor invoices from email and WhatsApp
• OCR and LLM field extraction mapped strictly to Tally ERP 9 ledger schemas
• A deterministic three-way reconciliation engine that routes its own discrepancies
• Idempotent RPA writeback into Tally ERP 9, so a record cannot post twice
• A finance exception dashboard for what the engine will not decide alone

The problem

Three to six months went into each target country by hand — import regulation, statutory certification, freight partners. High-value infrastructure tenders across Africa, South-East Asia and the GCC were missed because the compliance path was never mapped before the deadline.

What was built

• A market intelligence system tracking infrastructure spending and import tenders across 40+ countries
• An export compliance rules engine covering CE, GCC Conformity and SASO certification, HS codes and vetted bonded freight
• Corridor identification routing high-probability export opportunities into the sales pipeline

The problem

Every sale went through an offline middleman, taking 8–12% of gross margin with it. There was no direct buyer channel at all, and qualifying a high-volume buyer took days.

What was built

• Programmatic acquisition scanning industrial buyer networks and tender boards
• A buyer scoring engine reading credit signals, procurement history and volume capacity
• A live catalogue with inventory and price synchronisation, feeding a deal-stage CRM

The problem

When tier-1 national competitors withdrew from a region, the gap went uncaptured because the only signal was dealer chatter. Polymer prices moved faster than pricing decisions, which took weeks.

What was built

• Competitive intelligence nodes watching regional price lists, government tenders and resin exchanges
• A pricing and margin arbitrage engine surfacing regional spreads and unmet volume
• Procurement leads routed live into frontline sales

The problem

Fifty vehicles were dispatched through WhatsApp groups and spreadsheets. Consignees had no live visibility and no dependable ETA. Reconciling 40+ logistics vendors ran fourteen days behind with an 8% billing error rate.

What was built

• A logistics operating platform with live GPS telemetry and algorithmic route optimisation
• A consignee tracking portal with milestone messaging over WhatsApp and SMS
• Driver scoring, digital trip-sheet verification and automated trip payroll
• A six-stage financial pipeline across SAP Business One (read-only APIs with RPA writeback), Zoho CRM and exception routing

The problem

Shipping manifests, customs declarations and certificates of origin were assembled by hand, five to seven days per consignment, with roughly a 15% clerical error rate — and every error risked demurrage or a customs rejection at the far end.

What was built

• A documentation engine producing validated shipping packets and origin certificates from templates
• Multimodal freight routing across carrier schedules and customs brokerage networks
• A statutory compliance engine cross-checking cargo data against destination port rules before dispatch

The problem

Every campaign took two to three weeks of assembly by hand — itineraries, route logistics, pricing tiers, visual collateral. Slow launches pushed acquisition cost up.

What was built

• A generative content sprint framework for multi-destination collateral
• A personalisation engine generating day-by-day programmes, transit routes and pricing tiers per customer profile

The problem

Matching packaging variations to production work orders across the ERP, logistics portals and vendor threads was manual, and it put three to five days between an order and the ledger.

What was built

• A data pipeline consolidating production orders, packaging specifications and dispatch records
• Pattern matching resolving packaging variations to standardised parent SKUs
• Synchronisation between the ERP and the logistics TMS

The problem

Fifteen outlets each held their own data. Consolidating sales, inventory and cash took ten to fifteen days a month, by which time the picture was history and regional stock imbalances had already cost money.

What was built

• A pipeline extracting every branch’s transactions nightly
• One executive dashboard for branch inventory, revenue velocity and cash
• An exception engine raising stock-outs, slow-moving inventory and cash discrepancies

The problem

Factory scheduling and omnichannel demand were disconnected, so retail, wholesale and e-commerce could be out of stock and overstocked at the same time — with spoilage at one end and lost sales at the other.

What was built

• Order routing aggregating purchase orders across the ERP, distributor portals and e-commerce
• Demand sensing forecasting channel demand and adjusting factory batch schedules
• Content and pricing syndication across every channel listing

The problem

Wholesale billing was handwritten and posted late — five to seven days between the weighbridge and the ledger, and no visibility of cash in between. Nothing tracked lot aging or spoilage risk across the warehouses.

What was built

• A billing pipeline computing invoices from electronic scale readings, quality grades and live mandi pricing rules
• Writeback posting invoices straight into Tally ERP 9
• Lot aging and spoilage risk monitoring across warehouses

The problem

Positioned as plots among plots, the project met price resistance and lived on low-converting listing portals, where enquiries went cold before anyone replied.

What was built

• Repositioning from housing plots to master-planned community living
• A multi-stage acquisition engine on Google Search and Meta, into single-purpose landing pages built for 20%+ conversion
• WhatsApp CRM automation sending the brochure and booking the site visit within minutes

What was built

• A property discovery and land acquisition platform with dynamic parcel mapping
• Zoning compliance tracking and a verified broker directory
• Transactional workflows connecting institutional buyers, aggregators and developers

What was built

• Brand foundation moving the firm from drafting services to premium design consultancy
• An authority portfolio built around high-ticket commercial and residential work
• Inbound lead handling that filters for high-budget institutional prospects

What was built

• 3D packaging engineering — droppers, pump bottles, jars — and secondary folding cartons
• Print-ready production specifications: die-lines, materials, foil stamping
• A visual identity built to hold a premium shelf price

The problem

Four brands each waited four to six weeks on physically fabricated samples before a product could move, and paid for every sample.

What was built

• A 3D prototyping and rendering framework for photorealistic virtual sample validation
• A specification router dispatching validated CAD straight to manufacturing partners

What was built

• A clean-label positioning framework
• Consumer education funnels
• Retention sequences over email and WhatsApp for repeat purchase

What was built

• A B2B corporate digital identity
• Standardised digital catalogue schemas
• Multi-channel directory infrastructure for domestic distribution

What was built

• A complete visual identity system
• Technical die-cut packaging artwork
• Brand governance documentation

The problem

A community of hundreds, growing towards thousands, with its records, its welfare ledger and its introductions all held informally — and a strong requirement that none of it become public.

What was built

• A seven-table relational schema scaling from 250 to 2,500+ members
• Hierarchical family tree mapping (Shajra-e-Nasab) with approved lineage links
• Committee-gated matrimonial matching, with contact mediated offline to protect privacy
• A confidential welfare loan (Qarz-e-Hasana) and Zakat ledger: public aggregate counters, anonymous recipients
• An RSVP engine pulling nuclear family members for one-tap headcounts

What was built

• A four-pillar positioning: fresh hot meals, moral foundations, accessible fees, zero-risk trials
• Hyper-local Google Business Profile SEO for neighbourhood search
• RWA outreach playbooks and paediatric clinic partnerships
• A 24-hour admissions CRM protocol, structured trial-day tours and referral incentives
• An operational roadmap for 12:1 student-teacher ratios and smart classes

What was built

• A mobile-first, scroll-driven experience with 3D envelope-opening physics
• Royal architectural motifs and multi-day itinerary sequences
• Integrated guest RSVP and headcount tracking

Why we built it

Our own work needed one source of truth, or we would be selling operational discipline we did not practise.

What it does

• Client onboarding, scope definition, sprint decomposition, developer QA submission, change requests and staged approvals in one line
• Blocker detection and workload monitoring
• Revision audit logs

What it does

• CORE — co-pilot and daily task execution
• GROWTH — business modelling and go-to-market strategy
• OPTIMIZER — meta-prompt engineering and multi-agent evaluation
• TRADE — EXIM advisory and cross-border logistics

What it does

• Candidate pipeline tracking
• Automated résumé evaluation
• Interview scheduling and candidate communication

Why we built it

Fabrication in India is a decentralised trade: skilled specialists, no discovery layer, and no way for a buyer to find or trust one.

What it does

• A discovery directory onboarding fabrication specialists, welders and artisans
• Managed commercial jobs with a transaction fee model