Skip to content

Igor Lima · NiftyAi studio · El Cajon, CA

Stop paying people to copy and paste.

I am a Python developer in East County San Diego. I find the repetitive work eating your team's week, then build software that does it instead. Quotes, invoices, job reports, intake forms, the weekly spreadsheet nobody wants to touch.

Book the $500 audit See the work

Start here

The $500 automation audit

  • One week, start to finish
  • A written map of what is costing you hours
  • A ranked plan with fixed prices
  • Credited toward your first build

No retainer, no lock-in, no meeting about a meeting.

  • El Cajon / San Diego
  • Python automation
  • Fixed quotes
  • EN / PT / ES

Who it is for

Built for the businesses that run on spreadsheets and paperwork.

If a person on your payroll spends hours moving the same information between the same four places, that is the work I take off the table.

  • Contractors and GCs

    Bids, change orders, daily field reports, photo logs. Turn what your crew sends from the job site into the documents the office needs, without a night of retyping.

    • Field reports
    • Quotes
    • Job costing

  • Clinics and practices

    Intake, scheduling, records reconciliation, recurring reports. We scope exactly what data leaves your systems before a line of code gets written.

    • Intake
    • Scheduling
    • Reporting

  • Manufacturers and shops

    Production logs, inventory counts, QC sheets, purchase orders. Near Gillespie Field a lot of this still lives on clipboards and one fragile workbook.

    • Inventory
    • QC logs
    • Purchasing

  • Accountants and professional firms

    Client document intake, reconciliation passes, the monthly reporting grind. Repetitive, rules-based, high volume. Exactly what software is good at.

    • Intake
    • Reconciliation
    • Monthly close

How it works

Three steps. You can stop after any of them.

Most people start with the audit, do one build, and decide about the retainer later. That order exists so you find out whether I am any good before you spend real money.

  1. 01 About one week

    Audit

    $500

    I sit with you and your team, watch how the work actually gets done, and write it down. You get a map of every repetitive workflow, an honest estimate of the hours it burns, and a ranked list of what to automate first with a fixed price on each item.

    • Written deliverable you keep, whatever you decide next
    • Fixed prices on every recommendation
    • Credited toward your first build
  2. Most clients start here
    02 Usually two to four weeks

    Build

    $2,000 to $5,000

    Pick an item off the audit and I build it. Fixed quote agreed before I start, so the number does not move. You see working software every week, not a status update. At handover you get the code, the documentation, and a walkthrough.

    • Fixed price agreed before work starts
    • Working software demoed weekly
    • You own the code and the repository
  3. 03 Month to month

    Retainer

    Optional, monthly

    Some clients want someone on call once automations are running the business. Monitoring, small changes, the next thing off the list. Priced per client after the first build, cancel whenever. Plenty of people never need this and that is fine.

    • Monitoring and fixes on what is already live
    • A steady queue for the next items
    • Month to month, cancel anytime

Everything above is fixed price. If a build turns out to be bigger than the audit said, that is my estimate to fix, not your invoice to absorb.

Selected work

Things I built and shipped.

Live work you can click. Five pieces that follow one contractor job from the first enquiry through to the numbers after it closes, plus a couple of side projects that show how I build.

The contractor pieces are portfolio demos built for East County trades, not client case studies. Respond, follow up, win the job, ask for the review, check the books: each one is the step after the last. TrustLens and NiftyStats show other build patterns.

Instant Lead Response

Demo

Instant customer reply and owner SMS notify for trades

  • Automation
  • Lead response
  • Static demo
  • East County
Open the demo Read the code
Problem
The lead comes in while the contractor is twelve feet up a ladder in Santee. By the time anyone calls back that evening the homeowner has already booked whoever answered first.
Build
A click-through demo paced to the real clock. The lead lands, the customer gets a text back at eight seconds that names the job and asks one qualifying question, and the owner's phone buzzes at twelve with the name, the job, the city and how urgent it is. It sits next to Jobber or Housecall Pro rather than replacing either. Both paths are there: a web form, and a missed call where all you have is the number.
Result
A proof an East County contractor can click on their phone in under a minute. The page is labelled a demo in a header that never scrolls away, and it sends nothing. The done-for-you install behind it is the actual product.

Lead Follow-up

Live tool

Same-day text and email drafts for contractor leads

  • TypeScript
  • Vite
  • Browser only
  • Contractors
Open the tool Read the code
Problem
Website leads sit unanswered for a day or two. Whoever replies first gets the walkthrough, and it is almost never the person still finishing a job at six.
Build
A free browser tool that turns a CSV of leads into a ready-to-send text and an email for each one, urgent leads first, with a copy button on every draft. No account, no API key, and the list never leaves the device. A Python command line version mirrors it exactly for anyone who would rather run it from a terminal.
Result
Paste-ready drafts for today's leads, sorted by who needs a reply today. Open it on a link and try it with the sample data before deciding anything.

Ridgeview Remodeling

Demo brand

Lead-capture site for an East County remodeler

  • Astro
  • Tailwind
  • Lead capture
  • Demo brand
Open the demo Read the code
Problem
A weak contractor website loses the quote request before anyone finishes reading. No prices, no process, and no obvious way to ask for a number.
Build
A full marketing site for an invented brand: kitchens, baths and ADUs, the process spelled out step by step, honest price ranges instead of call for pricing, an FAQ, and a quote form that actually delivers. The sample reviews are labelled as samples on the page itself.
Result
A live demo of the kind of site I build for local trades, and the front end of the same lead loop the other two projects pick up.

Review Ask

Demo

The after-job Google review ask for trades

  • No dependencies
  • Review ask
  • Static demo
  • East County
Open the demo Read the code
Problem
The job is finished, the homeowner is happy, and nobody asks. The review that would have brought the next three customers never gets written, because asking is the one step that always falls off the end of the day.
Build
A click-through demo of the whole ask. One short message goes out by text or email, a gentle reminder follows only if the link was never tapped, and a thank-you goes out after it is. The homeowner lands on a small branded page with one button and nothing else on it. The wording is editable, and the editor refuses to save anything that offers a reward or asks only the happy customers.
Result
Every customer gets the same ask, and nothing is offered for a review, which is what keeps a real install on the right side of Google's rules. The page is labelled a demo in a header that never scrolls away, and it sends nothing.

Job Cost Odd-One-Out

Demo

The closed-job cost check for trades

  • TypeScript
  • Vite
  • Browser only
  • East County
Open the demo Read the code
Problem
The job closed, the numbers got typed in, and nothing looks wrong until the quarter is over. Most small books record the same spend twice, once off the job sheet and once off the supplier invoice, so every column looks like it moves together and the one line that does not fit hides in plain sight.
Build
Two dozen made-up closed jobs with labor hours, materials, parts, permits and drive time. One button scales each column against its own middle, folds the pair that turns out to be one spend recorded twice, then points at the job sitting farthest from the pack and the line that put it there. The reason comes back in two plain sentences rather than a wall of formulas, and Run again builds a different book so the answer moves.
Result
The odd job and the reason for it inside half a minute on a phone. It is linear algebra on a table of two dozen rows, not a forecast: it can say a line does not match the others, and it does not pretend to know whether that is a typo, a real equipment run, or a permit from a second agency.

TrustLens

Live beta on Base

Contract safety scanner and triage

  • Python
  • TypeScript
  • LLM triage
  • Cloudflare Workers
Open the live app Read the code
Problem
Raw contract scanners flag everything. Point one at a proxy contract and it screams about the same handful of patterns on every upgradeable token, so the real risks drown in noise nobody reads.
Build
A Python and TypeScript scanner that understands proxy patterns and triages findings by what actually matters for the contract in front of it, then explains each finding in plain language instead of a severity badge.
Result
Live in beta on Base. The triage layer re-judges every finding a raw scan produces and marks most of them false alarms, so what is left to read is a short list rather than a wall. Ongoing project, still being tuned.

NiftyStats

Live

Statistics in the browser, no install

  • Python
  • Pyodide
  • Pandas
  • Static hosting
Open NiftyStats
Problem
Anyone who wants to run a quick statistical test on a CSV has to install Python, pick packages, and fight an environment first. Most people give up and go back to the spreadsheet.
Build
Pyodide running real Python in the browser tab. Load a file, run the test, read the output. Nothing gets uploaded anywhere because nothing leaves the machine. Static hosting, no backend to pay for.
Result
A working stats tool anyone can open on a link. It is also the clearest demo I have of a pattern clients ask for: real computation, no install, no server bill.

Also built

  • NiftyVid · Video generation tooling and pipelines
  • MASTER Prompt Library · A working library of prompts I use in client builds
  • PolicyGuard · Defensive log classifier compiled into a DFA

About

I ran stores before I wrote software. It shows.

I spent years operating mattress stores. Payroll, inventory, vendors, the daily reports, the month that goes sideways because one number was typed wrong on a Tuesday. I know what busywork costs a small business because I paid for it.

Now I build the software that removes it. Python for the automation, TypeScript and React when something needs a face, Supabase when it needs to remember, hosted LLM APIs when the work needs judgment rather than rules. I study Applied AI at Grossmont and I am based in El Cajon.

I work with people directly. No account manager, no handoff to a junior you never met. You talk to the person building it, which is why the quotes are fixed and the timelines are short.

Based in
El Cajon, California
Languages
English, Portuguese, Spanish
Studying
Applied AI at Grossmont College
Works with
Local SMBs and remote US clients

What I build with

  • Python
  • TypeScript
  • React
  • Astro
  • Supabase
  • Pandas
  • LLM APIs

Questions

The things people ask before they book.

Anything not covered here, put it in the form below and I will answer it straight.

  • How fast does this move?

    The audit takes about a week from our first conversation to the written deliverable. Most builds run two to four weeks after that. If something is genuinely urgent, say so in your message and I will tell you honestly whether I can hit your date.

  • What do you need from me?

    Roughly two hours total during the audit. One walkthrough of how the work gets done today, a handful of real sample files, and access to whatever systems are involved. After that I work on my own and come back with something to look at.

  • Who is this not for?

    Companies that want a full ERP replacement, a ten person team, or an enterprise rollout with a procurement process. I am one person who ships focused tools fast. If you need a vendor with a sales department, I am the wrong call and I will say so on the first conversation.

  • What is not included?

    Third party costs stay yours: API usage, software licenses, hosting, any vendor fees the build depends on. I tell you what those run before you commit. Hardware and ongoing staff training beyond the handover session are also outside the quote.

  • Do I own what you build?

    Yes. Code, repository, documentation, all of it transfers to you at handover. No license to keep paying, and nothing that stops you from hiring someone else to extend it later.

  • What about sensitive or client data?

    We scope exactly what data the automation touches and what leaves your systems before anything gets written, and plenty of these builds never send data outside your own infrastructure at all. I sign NDAs. If your industry has specific compliance requirements, bring them to the first call so they shape the design instead of breaking it later.

Contact

Tell me what is eating your week.

A short note is enough. I read everything myself and reply within one business day. If it looks like a fit, the next step is a 30 minute call and then the audit.

Handled by Formspree. I never share your details with anyone.

Form giving you trouble? Email me straight at niftystudiodesigns@gmail.com.

Book the $500 audit