Founders without a technical partner
You know your market cold and you have a clear idea. What you don't have is someone who can turn it into working software and be accountable for it once real customers arrive.
Software that actually runs your business.
GOWIN Software Solutions builds custom software for independent founders and small teams — end to end, by one senior engineer who stays with the work long after it goes live.
Who I work with
I work with people who run the business themselves.
Not procurement departments or committees. If you are the person who feels the problem, you are the person I want to talk to.
Businesses outgrowing spreadsheets
Orders arrive on WhatsApp, stock lives in a notebook, accounts sit in Excel. It held together at ten customers a day. At a hundred it costs you stock, money and evenings.
Software nobody maintains
An app was built, the developer moved on, and now nothing can be changed safely. I take these over: document them, get them under test, and make them safe to touch again.
Services
Everything between the idea and a business running on it.
01
Product build, end to end
From the first conversation to a live product your customers use every day — interface, data, payments, deployment and all the unglamorous parts in between.
02
Business operations systems
Orders, inventory, scheduling, deliveries, refunds and a ledger that reconciles. The admin console your team actually lives in all day, built around how you already work.
03
Payments & customer sign-in
Checkout, payment gateway integration, one-time-password sign-in, refunds and reconciliation — built to survive real money, real customers and the awkward cases in between.
04
Automated testing & quality
Readable behaviour tests, end-to-end and API coverage, accessibility and visual checks, all running automatically on every change so releases stop being frightening.
05
Rescue & stabilise
Inherit an existing codebase nobody understands any more. I map it, document it, put it under test, fix what is bleeding, and give you back something you can build on.
06
Deployment & ongoing care
Cloud hosting, your own domain, backups, monitoring and a release process that runs the same way every single time — then someone who answers when it doesn't.
How I work
Four habits that keep small projects out of trouble.
Most software for small businesses fails for the same handful of reasons. These are the ones I design against.
01
Understand the business before writing code
I start by learning how your money moves and where your day disappears. Most software fails because it modelled the wrong thing — not because it was coded badly. That week of questions saves months.
02
Ship something small, every week
Working software you can click on, in front of you regularly, versioned and written up. No six-month silence ending in a surprise. If we are heading the wrong way, you will see it in week two, not month five.
03
Test it like it is already live
Automated tests run on every change — the customer journey, the payment path, the admin screens. When a release would break something, we find out before your customers do. This is the part most freelancers skip and the part that decides whether you can still change the system next year.
04
Hand over completely
You own the code, the accounts, the domain, the documentation and the deployment process — from day one, not at the end. If you ever want to work with someone else, you can, and nothing about that is difficult.
You own everything
Scope and price agreed in writing
One person accountable
Written down, not remembered
No lock-in
Selected work
What a finished engagement actually looks like.
Case study · Direct-to-consumer fresh produce
From a spreadsheet and a chat group to a platform that runs the day.
The business grew and sold perishable produce direct to households in residential communities. Orders arrived over chat, stock was counted by hand, and every delivery round ended with an evening of reconciliation. Nothing could scale — and with produce that spoils, every mistake was money on the floor.
I built the whole system, and I still maintain it: the customer app, the payments, the admin console the team works in, the test suites and the production deployment.
- A customer web app with mobile sign-in, live availability and a checkout that holds stock while payment completes — so two people can never buy the same last packet.
- Online payments with automatic refunds when an order cannot be fulfilled, reconciled against the books rather than tracked by hand.
- An admin console covering production scheduling, inventory movements, delivery slots, customer accounts, refunds and an income-and-expense ledger.
- Automated end-to-end, API, accessibility and visual-regression suites that run on every change, with published test reports.
- Production deployment on the client's own domain, with a staging environment, backups and a repeatable release process.
90+
documented releases, each with written release notes
4
automated test suites running in continuous integration
3
environments — local, staging and production
1
engineer, from the first sketch to live support
Capabilities
The toolkit, for the people who ask.
If none of this means anything to you, that is fine — it is my job to worry about it, not yours. If you have a technical adviser, hand them this list.
Product & interface
- React, Vite
- Progressive web apps (installable, offline-tolerant)
- Responsive, mobile-first interfaces
- Accessibility (WCAG-guided)
- Design systems and component libraries
Services & data
- Node.js, Express
- REST APIs with documented contracts
- MongoDB, schema and index design
- Scheduled jobs and background work
- PDF, Excel and CSV exports
- Email and push notifications
Payments & identity
- Payment gateway integration
- Refunds and reconciliation
- One-time-password authentication
- Rate limiting and abuse controls
- Audit trails and access logs
Quality & testing
- Cucumber BDD, Playwright
- Jest, Vitest, unit and integration tests
- API contract verification
- Accessibility and visual-regression checks
- Allure test reporting
- Load and performance testing
Delivery & operations
- GitHub, pull-request review, branch strategy
- GitHub Actions continuous integration
- Staged releases with versioned notes
- Cloud hosting and managed databases
- Custom domains, certificates, DNS
- Backups and restore drills
Working together
- Written scope and fixed milestones
- Weekly demos of working software
- Issue tracking you can see into
- Handover documentation and guides
- Training for your team
Tools are chosen to fit the problem. This is what I reach for most often — not a list I am limited to.
Engagements
Three ways to start, all quoted before we begin.
Discovery
We map how your business really works and agree what is worth building. You leave with a written plan, a costed build broken into milestones, and sketches of the main screens — yours to keep, whether or not you build it with me.
Delivery
Each milestone has an agreed scope, a price and a date. Working software demonstrated every week, code in your repository from the first commit, and tests written as we go rather than promised for later.
Care
Maintenance, monitoring, backups, small improvements and someone to call when something looks wrong. Most businesses need this more than they expect, and it is the cheapest insurance you will buy.
Everything is quoted in writing before work starts — no hourly surprises, and no invoice you did not see coming. Ask for a quote.
About
GOWIN is one engineer, on purpose.
I am Krishnan, and GOWIN Software Solutions is my practice. I build complete products rather than pieces of them — the customer app, the admin system behind it, the payments, the tests and the servers it all runs on.
I take on a small number of clients at a time, and that is deliberate. The person you have the first conversation with is the person who writes the code, runs the tests, does the deployment and picks up the phone when something goes wrong at eight in the morning. Nothing is handed down to a junior you never met, and nothing gets lost between a sales call and a delivery team.
I am based in India and work remotely with founders anywhere. My hours overlap comfortably with Europe, the Middle East and Asia, and I keep early and late slots for clients in the Americas.
If you are still weighing up whether your idea is worth building, I will tell you honestly — including when the answer is no, or when a spreadsheet and a bit of discipline is still the right tool for another year.
- Based in
- India — working with clients worldwide
- Works in
- English · Remote, with regular video calls
- Best fit
- Independent founders and businesses under 50 people
Get in touch
Tell me what you are trying to build.
A short email is enough to start. There is no form to fill in and nobody will chase you afterwards.
krishnan@gowin.net.in
What your business does
What is slowing you down today
Roughly when you need it working
A budget range, if you have one
I read and reply to every genuine enquiry within one business day. If it is not something I can help with, I will say so and point you somewhere better.