Skip to content

Selected Work

Engineering decisions that shaped real products.

A curated set of engagements where the constraint was never the framework — it was the business problem, the timeline, and the team you'd inherit the system tomorrow.

Each project below follows the same lens I bring to founder conversations: what made this hard, what we chose, and what changed because of it. Technology appears only where it explains a decision — never as the headline.


Selected Work

Building a Healthcare Collaboration Platform When Generic Networking Wasn't Enough

Healthcare innovation often fails because the right people never meet early enough. Splice — a Heroes of Humanity initiative — was built to connect doctors, engineers, founders, and investors around meaningful MedTech collaboration, not to compete with broad professional networks. The platform shipped as a private beta with a storytelling-first landing experience and a recommendation system designed for professional complementarity.

Role

Sole Engineer — architecture, product implementation, landing experience, compatibility logic, and private-beta readiness. Responsible for translating a collaboration vision into a platform where purpose is understandable before a user creates an account.

The Challenge

The problem was specific, not generic. Doctors understand clinical problems. Engineers know how to build. Founders drive execution. Investors understand commercialization. But most networking platforms are broad, noisy, and saturated — making it genuinely difficult to find healthcare-specific collaborators who complement rather than duplicate your skills. The product had to earn trust quickly in a domain where the cost of a wrong match is months of engineering effort aimed at the wrong problem.

Key Decision

Design the platform around collaboration outcomes, not profile browsing. The landing experience would tell a story — clinician, builder, founder, investor converging toward better healthcare products — before explaining features. Discovery would prioritize meaningful professional fit through complementarity and intent, not surface-level similarity. Same-city proximity, stated looking-for preferences, startup stage alignment, and role pairing would inform recommendations alongside profile data — increasing the likelihood of useful connections rather than endless scrolling.

Outcome

Splice reached private-beta readiness under the MedTechPreneurs brand within a phased delivery cycle. The client responded most strongly to the landing narrative — the clearest articulation of why the platform exists. The product now sits alongside Galactica and Academy within Heroes of Humanity, oriented toward a longer vision: helping the right people collaborate earlier so better medical technology products become more probable.

Read the full case study

Building a Medical Event Platform in 30 Days While Requirements Kept Evolving

Dr. Noor, Managing Head of a medical college, needed a complete event platform — passes, workshops, meals, cart, payments, and admin — in roughly thirty days. Requirements kept shifting throughout build, including a second event added near the end. The platform delivered on schedule; the architecture supported continued expansion after the event was postponed.

Role

Sole Engineer — responsible for architecture, implementation, deployment, and production readiness. AI-assisted development tools (Cursor and Claude) accelerated delivery; all engineering decisions, architecture, testing, and production ownership remained mine.

The Challenge

The hardest constraint was not the stack or the timeline — it was scope that would not stay still. Feature requests arrived continuously: custom landing page animations, new registration flows, meal and workshop selection logic, and — near the end of development — Medgala, a specialized networking event within Galactica that needed its own registration surface on the same platform. Each addition had to ship without destabilizing what was already in production.

Key Decision

Treat the product as one deployable with explicit domain boundaries, not a collection of pages built feature-by-feature. Separate marketing, registration, and admin concerns at the routing layer so new event surfaces (like Medgala within Galactica) could be added without rewriting the core registration and payment flow. Build the payment path to work with payments enabled or disabled, so registration could ship before payment credentials were final. Automate deployment from the first week so every change reached a production-like environment without manual steps.

Outcome

The event was later postponed due to academic scheduling — outside the platform's control. The software itself delivered successfully: the client continued the engagement, requested additional features, and the architecture absorbed that expansion without a rewrite. Fiesta Liva was renamed Galactica; the platform now sits under Heroes of Humanity alongside Splice and Academy.

Read the full case study

Multi-Project Real Estate Marketing Platform

A real estate broker launching developer campaigns faced a repeating cost: every new project traditionally meant another website — duplicated engineering, inconsistent branding, repeated SEO work, and expensive maintenance. The solution was a reusable marketing platform capable of powering multiple campaign sites from one foundation, each with its own domain, identity, and analytics.

Role

Sole Engineer — platform architecture, shared section system, multi-project deployment pipeline, SEO infrastructure, and lead capture. Responsible for designing repeatability into the foundation so future campaigns could launch without starting from scratch.

The Challenge

This was never meant to become a property marketplace. The broker's business model is launching authorized sales partner campaigns for developers — Prestige, Godrej, and others — each needing a conversion-focused microsite with compliant disclosure, independent SEO, and its own paid-traffic landing pages. Building a separate codebase per campaign does not scale: engineering effort duplicates, branding drifts, metadata conflicts arise, and every update becomes a maintenance event multiplied across sites.

Key Decision

Treat each campaign as a configuration of one platform, not a bespoke build. A configuration-driven page system would let new projects declare which sections appear and in what order — a long Prestige funnel with pricing and floor plans, an urban Godrej rhythm without the same depth, a Golden Doors broker hub routing visitors to live microsites — all from shared section components. Each campaign would ship as its own domain with baked canonical URLs, analytics, and theme, while sharing one maintainable codebase and deployment pipeline.

Outcome

What began as a single campaign site evolved into a platform powering multiple live properties: developer microsites for Prestige and Godrej, plus a Golden Doors portfolio hub linking outward to each campaign. New projects register as content and configuration packs rather than new applications. The broker gains faster launches, lower maintenance, consistent partner disclosure, and independent SEO per campaign — without multiplying engineering cost each time a developer relationship goes live.

Read the full case study

Have a technical decision you're not confident about? I work with founders on architecture, trade-offs, and delivery.


© 2026 BuiltByAyush Consultancy. All rights reserved.