CRMs, internal tools, AI agents and integrations for Chicago-area businesses, built and supported by the same person from start to finish.
Short answer
Custom software development in Chicago from Everyday Software means Jude Horak, one New Lenox engineer, builds what your business is missing: a custom CRM, internal tools and dashboards, AI chat and phone agents, a knowledge assistant, or automations between systems you already use. One person to call, testing on your own data, a quote after scoping.
Jude Horak scopes, builds and supports every project himself
call records a month flowing through a telecom billing pipeline I built
companies billed monthly off usage numbers that pipeline produces
of live AI phone agents, each tied into the customer's own software
Five steps, and you can see working software early instead of waiting for a big reveal.
You tell me what is slow, manual or broken.
I map your current tools and write down what the build will do.
I build the smallest useful version first and show it to you.
I run it against your real records, not made-up samples.
It goes live, and I keep adjusting it as your business changes.
Most requests I get fall into one of these six kinds of work, and many projects combine two or three.
A customer and deal tracker shaped around how your team sells and follows up, instead of a rented template you bend your process to fit.
Screens your staff use every day: order intake, job tracking, inventory checks, and dashboards that pull numbers from several systems into one view.
Chat and phone agents that answer customers, collect details and book or route the request, connected to the software you already run.
An internal assistant your staff can ask questions in plain English, answered from your own documents, records and procedures.
Connections between the tools you already pay for, so data moves on its own instead of being retyped from one screen into another.
Jobs that collect raw usage or sales data, total it correctly and hand finished numbers to billing or management without a manual spreadsheet step.
Real systems running today. Clients are described by industry only.
I am the only engineer. The usage pipeline I built takes in about 1.3 million call records a month from three carriers, and more than 3,000 business customers are billed monthly from its numbers, with nobody checking each line by hand. It also reconciles roughly 88,000 phone numbers across four separate systems.
I built the store's AI chat agent and the test harness that guards it: 50 customer scenarios, each run 10 times against the live agent, before a change ships. I also built a feature that turns a few photos a shopper picks into a personalized ring recommendation email in under a minute.
My system generates and syndicates about 2,000 boat listing records a day across the group's brands and three outside marketplaces, so listings stay current without staff re-entering them on each site.
Dozens of AI phone agents I built are live today. Each one is connected to that customer's own software, so a call can end with a record created or an appointment booked rather than a note someone has to retype.
There is no price list, because two projects with the same name can be very different jobs. These are the things that make a build bigger or smaller.
An offshore team can be the right call for a large, well-specified product with its own project manager on your side. For a business that knows the problem but not the technical answer, a nearby engineer in your time zone tends to fit better.
With me, the person on the call is the person writing the code. There is no account manager relaying your request, and questions get answered during your business day.
Businesses that have outgrown spreadsheets and copy-and-paste between apps, but do not want to hire an in-house development team. My current builds include a telecom provider, an online retailer and a yacht brokerage group, plus AI phone agents for businesses in several other industries.
If your staff spends hours a week moving data by hand or answering the same calls, that is usually a good place to start.
I am one engineer, not an agency with a bench of developers. That means you talk to the person writing the code.
I do not publish fixed prices. Every quote comes after a scoping call, because the cost depends on your systems and data.
AI agents are not a replacement for your staff on judgment calls. Plan on a person owning the cases an agent was not built and tested for.
I do not have an office in Chicago. I work from New Lenox, southwest of the city, so plan on calls and screen shares rather than a downtown office visit.
Everyday Software is based in New Lenox, Illinois, in the southwest suburbs, and works with businesses in Chicago and the surrounding suburbs. It is a one-engineer shop: Jude Horak handles the scoping, the build and the support.
Usually, yes. Much of my work is connecting tools a business already pays for, such as its CRM, phone system, store or billing software, and adding the missing pieces around them instead of replacing everything.
It depends on scope, so I do not list prices. The number of systems involved, the state of your data, any AI agent testing and the number of user roles all move the cost. You get a written scope and quote after a call.
I start with the smallest version that removes real manual work, put it in front of you, and grow it from there. That keeps the first step focused and lets your team shape what comes next.
I do. The same engineer who built it handles fixes and changes, so nothing gets lost in a handoff to a support desk.
Book a free call. I will ask how your business runs today and tell you plainly what I would build first.
We use optional analytics and marketing cookies to understand visits and enquiries. Your demo works with either choice. Privacy policy