software-architecture.aiSoftware that still holds up in two years.
Custom apps, AI systems and integrations with architecture, tests and maintainability from day one. Built solo, with the care the work demands.
Sound familiar?
When your tool shapes your business instead of the other way around, it's time for something that fits your brand and your processes.
Your service inbox has become the bottleneck.
Every question gets answered by hand. Standard helpdesks don't fix it, because they don't know your brand voice and don't have your founder knowledge.
What are Sinnvampire?Standard SaaS doesn't fit your brand.
Mail tools suggest generic drafts. Shop plugins force their workflows on you. You work around the software instead of with it, and the brand voice dilutes along the way.
Custom software was always a different league for your size.
Traditional agencies were never an honest option for solo founders and small brands. So you built around the software instead of having it built for you.
Why custom over standard.
Standard software covers eighty percent. The remaining twenty percent are often what makes your brand specific. Mailings should sound like you, not like a template. Service should answer in your founder voice, not from a FAQ database. For exactly that twenty percent I build software that fits your brand and your stack.
Clean architecture decisions before the first line of code. The difference between an app that grinds after three months and one that grows with your brand. I think the structure ahead, you stay on the business.
What does that look like in practice? Read the article
What I actually build.
From a brand voice layer on your mail tool to a custom app inside your shop, end-to-end from one hand.
Brand voice engines
Systems that write in your brand voice instead of the language-model default. Tuned to your founder knowledge, embedded where your stack allows: mail tool, shop, or editor.
Service triage and knowledge search
Layers on your helpdesk that pre-sort tickets, generate reply drafts in your voice and reach into your knowledge. You decide what gets sent. The system handles the routine.
Shop and mail tool extensions
Custom apps for shop platforms, dedicated flows in your mail tool, connections between shop, CRM and mail tool. So your data finally flows together.
Founder knowledge systems
Structured knowledge layers that capture how you decide, advise, reply. Your knowledge no longer only lives in your head; it becomes reachable for service, marketing, onboarding.
Web apps and dashboards
When you need your own app (customer portal, internal tool, reporting), I build it as a clean web application with modern architecture.
Stack and integrations
Stack-close means I build where your business already runs, instead of forcing a new system on you.
- Web and app: React, Next.js, TypeScript, Tailwind
- AI systems: production LLM applications, RAG with embeddings and vector stores, brand voice tuning
- Agentic patterns: MCP servers for tool integration, sub-agents for specialised workflows, agent skills as reusable building blocks, deployment patterns that survive in SMB environments
- Integrations: shop platforms, mail tools, helpdesks, CRMs, REST and GraphQL APIs
- Data: PostgreSQL, vector databases, event streams
- Operations: Docker, automated deployment, EU-hosted where it makes sense
Typical projects
- Brand voice engine, embedded in your mail tool and your shop
- Service triage layer with reply drafts in your brand voice
- Founder knowledge system for onboarding, service and marketing
- Custom app inside your shop or as an extension of your mail tool
- Customer portal, internal tool or reporting dashboard for small teams
How it runs
Describe the project
We discuss requirements, goals and constraints. As peers.
Concept and architecture
A technical concept with clear architecture, schedule and a transparent cost estimate.
Agile delivery
Development in short iterations with regular demos. You see where we are at any time. After the first milestone you decide. If it doesn't convince you, you pay nothing.
Handover and support
Clean documentation, deployment, walkthrough. After that I'm available for support and further development.
Optional
Grow together
On request I stay on after go-live: proactive optimisation, a monthly briefing, the security that the solution doesn't go stale but grows with you.
Architecture quality, priced for SMBs.
AI-generated code has a bad reputation. Understandable. What gets clicked together without architectural understanding leaves marks. Used right, AI isn't a substitute for expertise, it's an amplifier of it.
I've built my own development processes that integrate AI strategically into every step: from requirements analysis through architecture to testing. Architecture decisions, code reviews and quality assurance stay fully with me. The AI accelerates the build.
The result: software at a quality level that used to require enterprise budgets, at prices realistic for small companies.
How AI-supported development makes software affordable
What's behind the hype, why quality standards still hold and how custom software adds up for small companies.
Read the article→
Who's behind it
Over a decade of software architecture: from enterprise systems to lean solutions for small companies. The methods of large projects, without the overhead.
As a freelancer I know the reality of the people I work with: limited budgets, tight windows, no in-house dev team. Every solution has to work under those conditions.
“Good architecture isn't a luxury. It's the reason software still extends after two years.”
Freelance architect vs. in-house team
Now you know who's behind it. The remaining question: does an external architect make more sense than an in-house solution?
With a freelance architect
- Flexibly available exactly when you need me
- No recruiting, no overhead, no onboarding
- Instantly available expertise in software architecture and AI
- Tailored precisely to your project
- Transparent billing without fixed costs
In-house
- Lengthy recruiting for specialised profiles
- Fixed costs regardless of project workload
- Ramp-up time for architecture and technologies
- Additional management and administrative overhead
- Less flexibility with changing requirements
Both approaches have their place. For project-based architecture expertise, the freelance approach is often the more efficient path.
Does this fit your project?
So we both know from the start whether it fits.
Right for you
- You want professional software without needing an enterprise budget
- Your project is too unique for standard SaaS, but a traditional agency would be too expensive
- You value short paths: one point of contact from concept to deployment
- You want software that's cleanly built and can evolve over time
- You're looking for someone who thinks along, not just executes requirements
Not the right fit
- Your budget is below €4,000, where clean engineering with tests and architecture doesn't fit
- Your project needs a team of ten or more developers in parallel
- You need 24/7 managed hosting with SLA guarantees
- You're looking for a pure template website without custom logic
Happy to recommend the right partners for these topics. If you're unsure whether your project fits the corridor, let's still talk briefly.
Frequent questions
Sounds like you?
Describe your situation. I'll tell you honestly what can come of it.