Websites & applications
Websites that explain your business clearly, plus customer portals, web applications, and the backend systems behind them.
Independent systems consulting
I build websites, connect business tools, and develop practical AI workflows around how your business works.
Illustrative workflow: website requests, email, and project details come together for review.
When requests get lost in email or the same information gets entered twice, start with the workflow that needs to work better.
Bring a website that needs work, tools that don’t connect, or a manual process that’s slowing the team down.
Websites that explain your business clearly, plus customer portals, web applications, and the backend systems behind them.
Connect forms, email, and business tools so requests reach the right place and information doesn’t have to be entered twice.
Sort incoming requests, summarize information, or prepare translations—with human review built into the workflow.
Selected work
A practice website and a connected device product, each with software I built.
I built the practice website and its supporting backend. Visitors can find provider information, services, and patient resources.
I built the complete software for this router recovery and monitoring product, including customer accounts, a dashboard, device history, and notifications. The system is running in production, integrating Sonoff S31 smart plugs flashed with Tasmota.
Armaan Amirani
Founder & software engineer
I’m Armaan Amirani, a software engineer with senior and lead experience at DraftKings and a background at Flint Hills Resources, part of Koch Industries. I’ve worked on Marketplace, Reignmakers, and the new Jackpocket app.
I previously ran a web development business serving local companies. That experience shapes how I approach consulting: clear communication, practical decisions, and software that fits the business.
Start with what’s getting in the way. We’ll work out what’s worth improving.
Before building, I’ll work with you to define the scope, cost, timeline, and how we’ll assess the result.
Talk through the problem, the people it affects, and the tools already in place.
Agree on deliverables, cost, timeline, and what the first version needs to do.
Make progress in the open, test the important paths, and adjust together.
Prepare the work for launch, document what matters, and agree on any next support.