For companies
Software developer and sparring partner
Software that runs without me.
For founders and product teams
Find out whether your tech holds up.
Book an intro call- Clear scope
- result and duration agreed in writing before we start
- In writing
- a result you keep, even if it turns out negative
- Handover
- source code, accounts and docs are yours at the end
- 1 working day
- until you have a personal reply
Seven services, clearly defined.
Every service has a fixed scope and a tangible result. So you know what you get before we start.
For companies
Websites, web apps and mobile apps
For companies and organisations that need a new website, a customer portal or an app, or whose online presence no longer keeps up.
“Our website is showing its age, and our customers are asking for an app.”
I plan and build websites, web applications and apps for iOS and Android, from the first sketch to launch. They load fast, they are accessible, and your team maintains them afterwards.
What you get
- Concept, design and copy, together with you
- Websites with a system for editing the content yourself
- Web applications and portals with sign-in, roles and integrations
- Apps for iOS and Android, through to publication in the stores
- Accessible and fast, third-party services only with consent
- Training and handover to your team or operations partner
Result
A launched website or app with source code, documentation, training and 30 days of aftercare.
For companies
Custom software and SaaS
For companies whose processes no off-the-shelf software covers, and for teams building or evolving their own product or SaaS platform.
“No standard software fits how we work. We need something of our own that we can maintain for years.”
I develop business applications, internal tools and SaaS products, from architecture to handover. I rebuild legacy software step by step while it keeps running.
What you get
- Requirements and architecture, matched to your team and operations
- Business applications, internal tools and SaaS products
- Tenants, roles and permissions, integrations with your systems
- Rebuilding legacy software, with analysis and a roadmap first
- Automated tests, deployment and documentation from the start
- Handover to your team after every phase
Result
Working software with source code, tests and documentation, handed over to your team after every phase.
For companies
Automation with workflows, agents and AI
For companies where data is copied by hand between systems, requests pile up, or knowledge sits in documents nobody can search quickly.
“Every day we type the same data from one system into another.”
I connect your systems with workflows and use AI agents where they work reliably. Every agent gets clear permissions and an audit log, and we use real examples to measure how well it performs. After a workshop you get a quote for each process.
What you get
- Map your processes and pick the ones worth automating
- Workflows that connect your systems and take over routine work
- AI agents and assistants with clear permissions and an audit log
- Human approval wherever mistakes get expensive
- Test cases from real examples that show how reliably it works
- Handover to your team or your IT provider
Result
Working automations with source code, documentation and measured reliability, handed over to your team.
Typical projects
- Data between systems A workflow transfers and checks what someone used to type by hand, and reports discrepancies.
- Sorting incoming requests Enquiries, emails or receipts are recognised, assigned and passed on to the right place.
- An agent in your application An AI agent completes tasks in your business application, only with the user’s permissions and with an audit log.
- Ask your documents An assistant answers questions from your documents, cites its sources and has a tested hit rate.
For companies
Advice and sparring for complex projects
For CTOs, engineering leads and project owners facing a far-reaching technical decision or in the middle of a complex project.
“We are facing an architecture decision that will stay with us for years, and we want a second opinion.”
I am your sparring partner for architecture, infrastructure and scaling. I review designs, work through the alternatives and support your team during delivery. That can be a one-off review or a regular schedule.
What you get
- Architecture and design reviews with a written assessment
- Decision papers that compare options, risks and effort
- A review of infrastructure, deployment and operations
- Finding load and performance bottlenecks before they get expensive
- Workshops with your team
- Regular sparring with your engineering lead
Result
Written assessments and decision papers your team can act on, with or without me.
For founders and product teams
Tech check
For founders and small teams with a prototype or MVP built with AI tools, no-code or by an agency. Or with an idea that hinges on an uncertain core function.
“Our prototype was built with an AI tool. Will it hold up with real users?”
I read your code and review architecture, data model, access control and operations. You learn what holds up and what needs fixing before the next step. For an idea without code, I review the core function: possible approaches, services and risks.
What you get
- Architecture, data model and dependencies
- Access control, secrets and common vulnerabilities
- Deployment, backup and recovery
- For AI features: 10 to 20 test cases with real examples
- Report with evidence, traffic-light rating and actions by urgency and effort
- A walkthrough of the results together
Result
A written report with a traffic-light rating per area, documented findings and actions sorted by urgency and effort.
For founders and product teams
Technical due diligence readiness
For founders preparing a seed or Series A round.
“Our funding round is coming up in spring, and the investor has announced a tech DD.”
I review your product against the framework investors apply in a technical due diligence. You find the weak spots first and go into the review prepared.
What you get
- Architecture, code quality and technical debt
- Security according to the OWASP Top 10 and selected ASVS requirements
- Dependencies, licences and software bill of materials (SBOM)
- Infrastructure, backup and recovery
- Key-person risk and documentation
- Data room package and a mock interview
Result
A findings report like a real review, an action plan leading up to the round and a prepared data room package.
For founders and product teams
PoC sprint
For funded founding teams and product teams in established companies whose project hinges on an open technical question.
“Our project hinges on one question: is the AI good enough to build a product on?”
A proof of concept answers a technical question with a working experiment instead of assumptions. Typical questions: is the AI’s output good enough? Can AI be connected to your business application (MCP)? Does an assistant answer questions about your documents reliably? Will the solution handle the expected load?
What you get
- Define a hypothesis with stop criteria
- 15 to 30 test cases from real examples
- Build the PoC with the data and integrations it needs
- An evaluation of what works, what does not and why
- Handover of source code and results
Result
A working PoC with source code, documented experiments, known limits and a recommendation for the next decision.
From first call to handover.
Four steps, the same for every project. What happens in them depends on yours.
In phases with decision points
If a lot is still technically open, we split the work into phases. Each ends with a result, and you decide whether and how to continue.
Your project
-
Step 1: Intro call
In 30 minutes we go through your goal and where you stand. After that we both know whether I’m the right person for it.
Company Understand goals, users and existing workflows
Founder Clarify the vision and the open technical question
-
Step 2: Quote
You get a written quote with scope, result and duration.
Company Define pages, features and scope
Founder Define hypothesis, test cases and stop criteria
-
Step 3: Build and review
I build it myself. At agreed milestones we look at the result together.
Company Build the website or application and sign it off together
Founder Run the tech check, DD readiness review or PoC and evaluate it
-
Step 4: Handover
You get the solution or report, with documentation and training. From then on, it all runs without me.
Company Launch, training and handover to your operations partner
Founder Report, source code and a recommendation for the next decision
In the end, it’s all yours.
I build things so that you don’t need me afterwards. Every project where software is built therefore includes:
-
Source code in your hands
In your repository, with its full version history.
-
Accounts in your name
Hosting, domains and services belong to you, not to me.
-
Documentation
For operations, maintenance and everyone who works on it after me.
-
Training
Your team knows how to edit content and apply updates.
-
A named operations partner
Your team or your IT provider takes over day-to-day operations.
-
Aftercare
For websites and apps, 30 days for questions and small fixes after launch.
About
One point of contact, from start to finish.
You talk to the person who builds and reviews your software. Your project doesn’t get passed to a team you never meet.
I work with AI coding agents if you agree, and I read every line before it goes into your system. And if a standard solution is enough, I will tell you, even if it means I build nothing.
I take on only a few projects at a time, so each one gets the time it needs.
Alexander Hirschfeld
Software development and technology consulting
- Working together
- On site or by video
- Languages
- German, English
- Reply
- Within one working day
My principles
- Scope, result and duration are agreed in writing before we start.
- I build it myself and review it before I hand it over.
- You get a written result, even if it turns out negative.
- Source code, accounts and documentation belong to you.
- AI services only see your code and data with your written consent. Otherwise I work without them.
What I don’t do
- Permanent team augmentation and on-call support
- Reviews on behalf of investors or buyers
- Legal and tax advice, penetration testing
- Clickable prototypes without a technical question
Day-to-day operations are handled by your team or a named operations partner.
Technology I work with
Languages
- TypeScript
- Go
- Rust
- PHP
- SQL
Web and APIs
- Node.js
- Svelte
- Astro
- Vue.js
- GraphQL
- REST
Databases
- PostgreSQL
- MySQL
- MariaDB
- DuckDB
- Redis
- Dragonfly
Infrastructure
- Docker
- Kubernetes
- Helm
- Terraform
- OpenTofu
Cloud and code
- AWS
- Azure
- GitHub
- GitLab
Frequently asked questions.
- What does a project cost?
- That depends on scope and goal. After the intro call you get a written quote with a fixed scope.
- When can we start?
- I take on only a few projects at a time. I will tell you the earliest start date in the intro call.
- Who supports the solution after handover?
- Your team or a named operations partner, such as your IT provider. I hand over source code, accounts, documentation and training. For websites and apps, I’m available for questions and small fixes for 30 days after launch. I don’t offer on-call support.
- What happens if a check or PoC turns out negative?
- Then you know early and at low cost. You get the result in writing, with reasons and possible alternatives.
- Does due diligence readiness replace the investor’s due diligence?
- No. It prepares you for it. The review itself is carried out by the investor or a reviewer they appoint.
- How do you handle code and data?
- You decide whether AI services may see your code or data. Without your written consent I work without them and analyse everything locally. I delete all copies when the project ends. Source code and accounts belong to you.
- Can I get public funding for my project?
- German federal states run funding programmes for digitalisation projects. Whether your project qualifies is decided by the funding body. Many programmes require you to apply before the project starts.
- Does my project need to involve AI?
- No. I use AI where it solves a problem and leave it out where it does not. Whatever AI contributes during development, I review myself.
Can’t find your question? Write to me directly: kontakt@alexander-hirschfeld.de
What would you like to build?
Briefly describe your project, where it stands and your timeframe. I will reply personally within one working day.
Intro call: 30 minutes, free of charge
- By phone
- By video
- On site by arrangement
Simply write to me directly at kontakt@alexander-hirschfeld.de.