Software that does real work for a technical business
Technical businesses sell things that take explaining, and they run on work that takes tracking. Your customers ask detailed questions before they buy. Your staff move information between quotes, jobs and records all day. I build websites, customer tools, internal software and AI integrations that handle more of that work, so fewer details get lost along the way.
I work with you directly, from the first conversation through handover. The groups below are a starting point. Plenty of projects mix more than one.
Business websites and product presentation
A website that answers a buyer's first questions
Buyers in technical industries arrive with specific questions. Can this shop handle my material and quantity? Does this company work on my aircraft type? Will this product fit my system? A good website answers those quickly, shows the depth behind the answer, and makes the next step obvious.
I organize your capabilities, services and product information the way your customers look for them, and I make sure inquiries reach the right person with the details you need.
What you get
- Capability, service and product pages organized around how buyers search and compare
- Product and specification information people can scan on a phone at their desk or on the floor
- Inquiry and RFQ paths that collect useful details instead of just a name and "call me"
- Google Analytics and Search Console set up so you can see how people find and use the site
- Search fundamentals built in: clear page structure, titles, descriptions and fast pages
- A content structure your team can keep up to date
In my work: Trepanning Specialties organizes a machining company's services and capabilities around direct inquiry paths. MajesticJet structures a whole library of aviation guides around the reader's next question.
Customer-facing tools
Tools that help customers plan on your site
The most useful thing a website can do is help with the job the customer is already doing. A buyer converting units, sizing a system or comparing options will come back to a site that helps them do it. And when they're ready to ask for a quote, they already know what they need.
Where it helps
- Engineering calculators and unit converters for the measurements your customers work with
- Product selectors and compatibility checks built on your actual product rules
- Comparison tools that put options side by side in the terms buyers care about
- Planning forms that turn loose requirements into an organized brief
- Guided quote intake that asks the right follow-up questions based on earlier answers
What you get
- A working tool on your site, designed for desktop and mobile
- Logic based on your rules and reference data, which you review before launch
- Results that lead to a relevant next step, such as an inquiry, a product page or a saved plan
- Measurement that shows which tools get used and where people stop
In my work: Trepanning Specialties has a live engineering unit converter. The Aircraft Sales Corp mission planner organizes aircraft requirements, model comparisons and questions into a brief. LiFePO4Batteries.net pairs sizing tools with a conversational adviser.
Internal software
Software for the work behind the quote
A lot of a technical business's day runs on spreadsheets, inboxes and memory: a quote revised three times by email, an approval that happened in a hallway, a job whose real costs nobody compared with the estimate. Software built around your actual workflow keeps those steps connected and visible.
Where it helps
- Quote workflows with versions, line items, approval thresholds and a record of what changed
- Job and work-order records that stay linked to the quote they came from
- Dashboards that show what's open, waiting or overdue
- Reporting on wins and losses, job costs and estimate accuracy
- Integrations that move data between the systems you already use, so nobody has to type it twice
What you get
- A working application built around your process, released in stages you can test with real work
- Roles and permissions matched to how your team actually works
- Records and reports you can export and use elsewhere
- Documentation of how the system runs and what it connects to
In my work: Check MRO links aircraft-maintenance RFQs, quotes, approvals, work orders and actuals in a single workflow. The Icarus IFE operator modules manage content, fleet configuration, announcements, licensing and reporting. Behind Aircraft Sales Corp, a private application organizes partner discovery and pipeline work.
AI assistants and automation
AI that knows your business and knows when to hand off
AI is useful when it takes on a defined job: answering the questions your staff answer every day, getting a messy request ready for review, or turning a pile of notes into something readable. I design assistants and automations around tasks like these, connect them to information you've approved, and route anything that needs judgment to a person.
Here are the kinds of applications I build. They're starting points for your business, and I shape each one around your products, documents and workflow.
An inquiry assistant for a machine shop
A visitor asks whether you can make a part. The assistant explains your capabilities using company material you've approved. Then it asks what your estimator would ask: material, dimensions, quantity, drawings, timing. What reaches your team is a fuller RFQ for a person to review, which beats a one-line "can you quote this?" every time.
An assistant that knows your products and business information
Customers and employees ask the same questions over and over. An assistant connected to your service pages, manuals, product sheets and policies can answer them in plain language and point to where the answer came from. When a question falls outside what it knows, or a person should handle it, the assistant says so and hands it off.
A product adviser
Some products need a conversation before a purchase: compatibility, sizing, what else has to change. A product adviser combines structured product rules with a conversational interface, so buyers can describe their situation in their own words and still get guidance based on your actual catalog. LiFePO4Batteries.net shows the pattern with a battery adviser connected to sizing tools.
Document-assisted quoting
RFQs arrive as PDFs, emails and spreadsheets. Document extraction pulls out the key details and drafts a structured intake record. Staff check and correct it before anything goes into a quote. Check MRO demonstrates this workflow for aircraft maintenance.
Help with internal paperwork
Summarize long job notes, flag a work order that's missing information, draft routine replies, or put together a weekly report from sources you've authorized. These are small, specific jobs, and together they give your team back real time.
Clearer software operations
If your business runs automated systems, it helps to see what they found and what someone decided to do about it. I build tools that turn logs and changes into readable briefs and keep a record of decisions. Recordant does this, with MCP tools that let an AI assistant review and record findings.
Private and locally hosted assistants
Some information shouldn't leave your building, and some places don't have a reliable connection. I can deploy suitable models on hardware or infrastructure you control, connect them to an approved knowledge base, and build the assistant into your website or internal software. Icarus IFE includes Anna, an assistant designed to hold onboard conversations without a cloud connection.
How these assistants are put together
Connected knowledge comes first. Most business assistants don't need a custom-trained model. They look up your approved material when a question comes in and answer from it. When you update a document, the assistant draws on the new version. Fine-tuning, which changes the model itself, is a separate and more involved step, and only a few specific cases call for it.
Where it runs is a design choice. An assistant can use a cloud model, a model on your own hardware, or a mix. I recommend one based on performance, connectivity, cost and how sensitive the information is. If an assistant on a public website has to keep data private, that boundary is designed into the hosting from the start.
People stay responsible for decisions. Assistants draft, sort, summarize and suggest. Quotes, approvals and commitments to customers go to a person. I build in clear handoffs, and I test assistants against real questions from your business before they go in front of customers.
Improvements to existing systems
Fixes and extensions for what you already have
You don't always need something new. Sometimes the website works but the inquiry form fails quietly. The internal tool does most of the job but is missing one report. Or the system the last developer built has nobody left who understands it. I take on focused work like this and scope it to the actual problem.
Where it helps
- Diagnosing and fixing specific problems in an existing website or application
- Adding a feature, report, integration or customer tool to a system you already use
- Cleaning up and documenting a system so someone can maintain it
- Ongoing maintenance, arranged to fit what the system needs
What you get
- A clear write-up of what I found and what I recommend, before larger changes begin
- Focused changes, tested against how the system is actually used
- Notes on what changed and why, so the next person isn't starting from zero
In my work: Several projects in my portfolio have been extended and restructured over time. Recordant began as a diagnostic layer inside a larger research system before I extracted it into a standalone product.
Tools and technology
Chosen for the job and for whoever maintains it next
I choose tools based on what the project needs, what you already run and who will look after it later. These are the tools I've used in the projects on this site, grouped by the job they do.
| What it does | Tools | Where it shows up |
|---|---|---|
| Web interfaces | HTML, CSS, JavaScript, TypeScript, React, Blade, Tailwind CSS, Vite | Trepanning Specialties, Check MRO, Icarus IFE, LiFePO4Batteries.net |
| Applications and services | PHP with Laravel, Python with FastAPI, Node.js | Icarus IFE, Mentor Sentinel, Check MRO, LiFePO4Batteries.net, MajesticJet |
| Data and storage | PostgreSQL, SQLite, Redis, S3-compatible storage | Check MRO, Mentor Sentinel, MajesticJet, Aircraft Sales Corp |
| Hosting and delivery | Docker, AWS, Cloudflare, nginx | Deployment and hosting across projects |
| Measurement | Google Analytics, Google Search Console | Website projects |
| Maps, 3D and realtime | MapLibre GL, Three.js, WebSockets and realtime messaging | Icarus IFE Atlas flight map, Mentor Sentinel dashboards |
| Data processing and scheduling | pandas, TA-Lib, CCXT, APScheduler | Mentor Sentinel |
| AI integration | OpenAI SDK; Anthropic, OpenAI and Gemini model adapters; MCP interfaces; offline assistant design; document extraction with staff review | LiFePO4Batteries.net, Recordant, Mentor Sentinel, Icarus IFE, Check MRO |
| Testing | pytest, Node.js built-in test runner | Recordant, LiFePO4Batteries.net |
How I use AI to build
I use AI-assisted development tools to move quickly. I decide what gets built, I check and test the output, and I'm responsible for the result.
Other options for a new build
If you already run a CRM, ERP, accounting package, shop-management system or a particular hosting provider, I start there and build around it. For a new project, I can evaluate other frameworks, databases, hosting options, AI model providers and local model runtimes against your requirements. If a tool is new to me, I'll tell you so plainly and plan for it.
Pricing and scope
Every project is priced from an agreed scope. Tell me what you need, and I'll work out a plan and a price with you before any work starts.
Tell me what you'd like to build
Describe the problem in a few sentences. If it's a fit, we'll work out the scope together.