Tirth Parikh / AI & automation engineering Fig. 00 · Signal Dubai · GMT+4

I automate the busywork.

I engineer AI agents, browser automation and the software around them, so repetitive work runs on its own and your team gets its hours back. Built to run in production, not to demo.

01/07The argument continues ↓
§01 · Friction

Your team is doing work a system should be doing.

  • 01"We copy the same data between three portals every morning."
  • 02"Support answers the same forty questions all day."
  • 03"We bought an AI tool. Nobody uses it, because it can't touch our systems."
  • 04"The weekly report takes a full day to put together."
  • 05"The prototype worked. Production is another story."
Fig. 01 · One operations morning
Illustrative · a composite of common requests Total  2h 40m
§02 · Systems

Six things I build. One way of building them.

Each system is engineered the same way: scoped access, logged actions, failure alerts and docs you own. Pick one, then replay a trace of it running.

    S1↑ ↓ to browse

    Does
    Built with
    You get
    trace.log
    idle. run a trace to watch it work.
    §03 · Process

    From first call to running system.

    A fixed scope and a fixed quote before work starts. Working software every week while it's built.

    1. 01

      Discovery call

      Thirty minutes, free. What's manual today, which tools you use, and what "done" means.

      A clear problem
    2. 02

      Written brief

      Scope, architecture, timeline and a fixed quote, in writing, before anything is built.

      A plan & price
    3. 03

      Build

      Weekly demos of real, working software. You can steer at every step.

      A tested system
    4. 04

      Launch & handover

      Deployment, monitoring, docs and a support window. Ongoing care if you want it.

      A system you own
    §04 · Fit check

    If you want a quick demo, I'm the wrong call. If you want something that runs every day without you, keep reading.

    Mark what's true for you. The reading updates below.
    Built for0 marked
    Not built for0 marked
    Reading

    Nothing marked yet.

    §05 · Engineer

    One engineer, the whole system.

    I'm Tirth Parikh, a full stack engineer based in Dubai. Day to day I build a product-based SaaS and its AI agent platform: MCP servers, agent automation and retrieval on vector databases, plus the FastAPI, Django and React around it and the DevOps underneath.

    Before that I shipped LMS and e-learning products used by paying customers, led Playwright test automation, and worked as a network engineer, which is where I learned to care about systems that keep running. You work with me directly, with no account managers and no hand-offs.

    Tirth Parikh
    Tirth Parikh · Engineer
    RoleFull stack & AI engineer
    FocusAI agents, MCP, browser & workflow automation, SaaS
    StackFastAPI · Django · Python · React · Redux · Node · Playwright · vector DBs · Linux · Nginx · CI/CD
    NowSoftware Engineer, SaaS & AI agent platform (2026 →)
    BeforeContent Enablers: MERN, LMS with SCORM/xAPI, Playwright (2023–25) · Orange Business Services: network engineering (2021–22)
    EducationMS Computer Science, Woolf (2027) · B.Tech, Nirma University
    BasedDubai, UAE (GMT+4) · working worldwide
    Certifications08 entries
    Jan 2026Databases & SQLScaler · Skill Mastery
    Jan 2026Data Structures & AlgorithmsScaler · Skill Mastery
    May 2024Custom SCORM TrackingUdemy
    Jul 2023PythonCoding Wise
    Jun 2023Full Stack Web DeveloperSolar Secure Solutions
    May 2023JavaScriptHackerRank
    Feb 2023Certified Frontend DeveloperCrio.Do
    2020Flipkart Grid ChallengeTop 46 of 4,000+ teams
    §06 · Questions

    Before you ask.

    01What does a project cost?

    It depends on scope. After a free call you get a fixed quote for well-defined work, or a monthly retainer for ongoing automation and support. No surprises later.

    02How fast can you start and deliver?

    Small automations often ship in days. AI agents and SaaS MVPs usually take a few weeks. The brief gives you a concrete timeline before anything starts.

    03Can you work with my existing code or team?

    Yes. I can extend an existing codebase, plug into the tools you already use, or work alongside your developers.

    04Is browser automation reliable?

    Built properly, yes. Playwright with retries, screenshots on failure and alerts, so when a website changes you know within minutes, not weeks.

    05What happens after launch?

    Deployment, documentation and a support window. If you want, I keep monitoring and improving it on a retainer.

    §07 · Project brief

    Describe the problem.

    → Read by: the engineer who'd build it → Reply: within one working day → Or: message on LinkedIn ↗
    01 · Where is it today?
    02 · What do you need? (any)
    03 · Describe the process or system
    04 · Your name
    05 · Where should I reply?
    0/5 fields · a few words is fine