I build software that reduces manual work.
I'm Jeremy Fischer, the software engineer behind Solutioncraft LLC.
I develop internal tools, connect existing systems, and automate recurring tasks for Twin Cities businesses.
Solutioncraft LLC develops custom software for businesses in Minneapolis–Saint Paul.
I start with
a specific problem.
I begin by understanding your workflow, existing tools, and operational constraints.
We identify where manual effort, errors, or delays occur. I evaluate improvements to your existing tools and available software before proposing a custom build.
We map the current process.
We identify the steps, people, and systems involved, including the workarounds your team relies on.
We assess the impact.
We examine how often the problem occurs and its effect on time, accuracy, and delivery.
We define the next step.
We agree on the scope and how to evaluate the result before committing to a build.
You'll work directly with me.
I'm Jeremy Fischer, a software engineer based in the Twin Cities. I run Solutioncraft LLC and develop custom software for business operations.
We can discuss the process you want to improve, the systems involved, and the constraints a solution needs to meet.
You can start with a specific task.
Describe what happens today, where it causes difficulty, and what you've already tried. That gives us a concrete starting point for discussing your options.
You'll know
what to expect.
Email me with the process you'd like to improve and the tools you use. I'll reply to arrange an initial discussion about the problem, your priorities, and whether I can help.
That discussion does not commit you to a project. If there's a fit, we define the next step and its scope before any paid work begins.
Will I need custom software?
That depends on the problem. An existing product, a configuration change, or a simpler process may be enough. I consider custom software when those options don't meet your requirements.
How are cost and timing decided?
We first define the scope, the systems involved, and what a successful result looks like. I then outline the proposed work, estimated cost, and schedule, including assumptions and dependencies. We agree on these before that work begins.
What happens after delivery?
We discuss documentation, software ownership, hosting, and ongoing support before a build. The proposal defines the handover and support responsibilities so you can plan how the software will be operated and maintained.
Help me understand
recurring operational problems.
I'm inviting people at Minnesota businesses to discuss manual processes, software limitations, and recurring bottlenecks. This research will inform future software offerings.
If you manage operations, lead an engineering team, or handle these tasks yourself, I'd welcome your perspective. You can also introduce me to a colleague with relevant experience.
Plan for a 25-minute conversation.
We'll discuss a task you've handled recently.
- You'll describe a recent task or incident.
- We'll discuss the tools and workarounds you use.
- We'll look at where your time or attention goes.
The interview is for research and does not include a sales pitch.
Let's discuss your next improvement.
Email me with the process you'd like to improve and the tools you use today.
I'm based in the Twin Cities.