AI automation for Indianapolis businesses

I build the internal tools and last-mile automations your team keeps working around: the manual report, the spreadsheet hand-off, the data someone types twice. The hours go back to the work only people can do.

What I build as your AI automation consultant

Small, finished pieces of software, each one removing a tedious step. Together they are how a business becomes genuinely digital.

Internal tools
A screen your staff actually use in place of a shared spreadsheet: look something up, update it, approve it.
Hand-offs between systems
Data that moves from one system to the next on its own, instead of being exported, cleaned up and typed in again.
Applied AI, where it earns its place
Reading documents, sorting incoming requests, drafting the first version a person checks. AI for a real problem, not for its own sake.
Reports nobody has to assemble
The weekly report someone builds by hand, generated and delivered on schedule.

One example: Perishable Shelf Stacking replaces the paper shelf-life list grocery stockers work from with a searchable product card showing the sticker date and the exact shelf locations.

Built on Next.js and AWS Amplify: fast pages, sign-in that keeps internal data internal, and serverless hosting that costs little when nobody is using it.

A good fit for Indianapolis teams when

  • There is an internal tool or manual hand-off that people have quietly built a workaround for.
  • The work is real but small enough to finish — weeks, not an open-ended engagement.
  • You want the reasoning and the specs handed over, not just a repository you cannot change.

I’m Yampier Medina, a Forward Deployed Engineer based in Indianapolis. I work with businesses in and around the city, in person when that helps and remotely when it doesn’t.

How an engagement runs

  1. A short call

    Thirty minutes on the problem itself — what it costs, who it touches, and what a fix would have to do to count.

  2. A written spec, before any code

    Requirements, design and a task list you approve. Nothing gets built from a conversation neither of us can go back and read.

  3. Shipped, and verified on staging

    Implementation against that task list, proven on a preview environment, and released deliberately — never by accident.

Every step is written down and verified before the next one starts. See the whole workflow.

Tell me what your team keeps working around

A short note is enough. I read everything and reply within two business days.