SaaS development & management
We design, build, and then actually operate SaaS products, including our own. That means we own the boring parts too — deployment, monitoring, updates and support, not just the first release.
We build software for other businesses — and then we run it.
A small, senior team in Kaunas. Automation, AI assistants, cloud, and SaaS products — delivered, then looked after.
What we do
Five things we're genuinely good at
We take on work we can own end to end — build it, ship it, and keep it running afterwards.
Automation & AI-driven workflows
For companies and individuals. We find the repetitive work in your business and replace it with automated workflows — including AI where it genuinely helps, rather than where it merely sounds impressive.
AI chatbots for your website
Assistants that talk to your potential customers, answer their questions and qualify leads around the clock — trained on your own business content, not generic web scrapings.
Cloud presence
We set up and manage your company's cloud infrastructure so it is secure, predictable, and something you can actually reason about — rather than a bill nobody can explain.
Website renewal & UX
Outdated website? Not a problem. We modernise it and give you concrete UX recommendations, so it works for the people who actually use it — and we'll tell you plainly what's wrong with it today.
Our own product
We ship our own software, not just other people's
The fastest way to judge how we work is to look at what we've built for ourselves.
Live · open for early access
Sugibana Flow
Multichannel inventory you can audit. Ledger-based stock and order management for EU sellers — built for people who are just getting going, and who need to trust every number they see.
- Real-time stock sync across channels, with oversell-safe reservations
- A full audit log of every stock movement — nothing changes without a trace
- Aya, a plain-language assistant for inventory, orders and channels
- Amazon is live today; eBay, Shopify, Etsy, Allegro, PrestaShop and TikTok are landing channel by channel
- Interface in six languages — English, German, French, Spanish, Polish and Lithuanian
How we work
Three steps, and no surprises in the middle
Most of the risk in a software project is not technical. It's not knowing where things stand.
We work out what you actually need
A conversation, not a discovery invoice. We look at how the work is done today, where it hurts, and whether software is even the right answer. Sometimes it isn't, and we'll say so.
We build it in the open
Small, visible increments you can react to. Documentation as we go, not written up at the end. You always know what's done, what's next, and what it costs.
We keep it running
Deployment, monitoring, updates and support. We don't hand over a repository and disappear — the thing we build is the thing we look after.
Why Sugibana
What you get that you might not elsewhere
-
We ship our own products
Sugibana Flow is live. We run the same stack we sell, which means we find the sharp edges before you do.
-
You talk to the person building it
No account-manager layer, no handoff to a junior team once the contract is signed.
-
EU-based, in Kaunas
Your data and your contracts stay inside the EU, under GDPR. No transfer paperwork, no grey areas.
-
Documentation-first and security-minded
Written down as it's built, so the knowledge doesn't live in one person's head — including ours.
-
We take over the parts nobody wants
Ongoing operation and maintenance, not just delivery. The unglamorous half is where software actually lives or dies.
The founder
Edmundas Adamonis
Automation, AI-driven workflows, and the chains of processes a business actually runs on.
More than ten years in IT, most of it building and running cloud infrastructure and the automation around it. The sharpest lessons came from building and operating Sugibana Flow, our own SaaS — you learn things running your own product that you never learn advising on someone else's.
AI is the right tool for most companies to improve what they already offer and to stand up something new quickly — used where it genuinely helps, not where it merely sounds impressive.
Worked with Azure · Terraform · CI/CD · Azure DevOps · Docker · Git · Python · PowerShell · Bash · REST APIs · Monitoring · Next.js · PostgreSQL · n8n · Cloudflare
Contact
Tell us what you're dealing with
You'll get a straight answer from the person who'd be doing the work.
What we'd ask you anyway. Answer what you can in the message — it saves a round trip.
- Which process, start to finish — what sets it off, and what counts as done?
- How often does it run, and how long does it take by hand today?
- Which systems does it touch, and can you already get API access to them?
- When it gets something wrong, who decides what happens next?
- If it fails at 2am, who notices, and how?
- Who is it for — your customers, or your own team?
- Beyond answering, what may it actually do: book, refund, escalate?
- Where does its knowledge come from, and who keeps that source current?
- What must it never say or do, and who signs that off?
- How will you know it's working — deflection, resolution, something else?
- Who pays for it, and what do they use instead today?
- What's the smallest version that would still be genuinely useful?
- Is there a real deadline behind this — funding, a contract, a launch?
- Once it's live, who owns the product decisions?
- What's the budget range, and is it a one-off or a monthly line?
- What are you running now, and where?
- What's the actual problem — cost, reliability, release speed, compliance?
- Is there anything that can't go down, and for how long at most?
- Who has production access today?
- Any data-residency or regulatory constraint we should know up front?
- What is the site failing to do — traffic, enquiries, credibility, speed?
- Who can approve copy and design, and how fast do they move?
- Is the content written, or does it need writing?
- What has to carry over — URLs, rankings, integrations?
- Who keeps it updated after launch?
- What's the problem, in the words you'd use to a colleague?
- What have you already tried?
- What does solved look like in three months?
- Who else has to agree before this goes ahead?
- Is there a date this must be done by, and what makes it that date?