Skip to content
Edishan Lee TenorioAI Automation Specialist & CRM DeveloperSoftware Engineer · Full-Stack Developer · Mobile Developer

Software that platforms can't buy.

Custom CRMs, SaaS products, dashboards and APIs, built in React and Next.js on the front and Node.js, Laravel or Java Spring Boot on the back. 17+ applications shipped to production, including revenue-generating platforms.

Scope

What I build.

Because I build automation too, the applications I ship come with the webhooks, events and APIs your CRM and workflows need to plug straight in.
  1. 01

    Custom CRMs & SaaS products

    Multi-tenant applications with role-based access, billing and the domain logic your business actually runs on: clinics, rentals, bookings, memberships.

  2. 02

    Web applications

    Fast, accessible React and Next.js front ends with a shared component system, so new features ship without the UI drifting.

  3. 03

    Backends & APIs

    REST APIs in Node.js, Laravel or Spring Boot, with clear contracts, authentication (JWT, OAuth, RBAC) and documentation another developer can pick up.

  4. 04

    Payments & integrations

    Stripe and PayMongo, geolocation and mapping, third-party catalogs and data feeds, wired in with idempotency and error handling.

  5. 05

    Admin dashboards & data

    Operations portals for inventory, scheduling, analytics and content: the back office that turns a product into a business.

  6. 06

    Cloud & deployment

    AWS (EC2, RDS, S3, Lambda), Vercel, Azure and VPS environments with CI/CD, plus the maintenance after launch.

Process

How an engagement runs.

  1. 01

    Diagnose

    We walk through the workflow as it runs today: where time goes, where data is re-typed, where leads go cold.

  2. 02

    Design

    I propose the system: which parts the platform handles, which need code, and how failures get caught.

  3. 03

    Build

    Implementation in short, reviewable increments, tested against real data before anything goes live.

  4. 04

    Launch

    Go-live with documentation for every trigger, input and failure point, team training, and support if you want it.

FAQ

Questions, answered.

01Which stack do you recommend?

Usually Next.js and TypeScript on the front, and Node.js or Laravel behind it. I'll match what your team can maintain, and I'll say so when an existing platform is the better call.

02Can you work inside an existing codebase?

Yes. A lot of my work is extending existing products: new modules, integrations, refactors and production support.

03Do you handle deployment and maintenance?

Yes, from first deploy through long-term maintenance, on AWS, Vercel, Azure or your own servers.

Next step

Have an application that needs building?

Tell me about the workflow that's slowing you down, the systems you need connected, or the application you want to build. We'll work out the right approach.