LASIKUU works end to end. Pick one piece or the whole arc, in English, Japanese, or Finnish.
We take a product or feature from design through implementation, release, and the rounds of improvement after. A good fit for teams building out their engineering org, or at a stage where hiring a tech lead is hard. Web and backend, design and data, handled as one piece of work rather than a stack of separate invoices.
Two sides of the same craft. We build AI into products, language models, retrieval over your own data, assistants, and agent workflows, in the places where they earn their keep, with the plumbing around them done properly: evaluation, guardrails, cost control, and fallbacks. We also help existing teams adopt AI in their own work, introducing coding assistants and AI-assisted workflows for developers, with sensible practices instead of hype. When AI is the wrong tool, we will say so.
A standing technical sounding board: architecture reviews, hiring, and AI strategy, for the moments when you want one more perspective before committing time and budget. We also put decisions on the record, with architecture decision records (ADRs) and clear documentation, so the reasoning behind a choice is still there when it matters. Useful as a one-off second opinion or as a continuing relationship, including steady upkeep once software is live.
When you need hands inside the team rather than a vendor at arm's length, we embed directly, remote day to day with on-site visits when they matter, for a sprint or a season. We learn your codebase, sit in your standups, and ship the difficult parts alongside your engineers.
The work of making separate systems work as one: internal tools, AI workflows, and data flowing where it needs to. It often comes up in the middle of building a product, and it is just as often a job worth doing on its own.
No hidden rate card games. Here is how an engagement is scoped and billed.
We start with a short conversation, then a written estimate and plan. You see the shape and the budget before any work begins.
Work is billed hourly within an agreed project budget. One-time fixed engagements are possible when the scope is clear.
Credit card or bank transfer, processed through Wise. Japanese consumption tax applies for domestic transactions. Terms are set out in the contract.
English, Japanese, and Finnish. Meetings, documents, and code comments can be in whichever fits your team best.
Yes. Most work is remote, and we can also work on-site within Japan when a project calls for it, including forward-deployed engagements inside your team.
Send a short message by email, Telegram, or LINE describing what you are working on. We reply with a few questions, then a written estimate and plan.
Unless we agree otherwise in the contract, the intellectual property of delivered work transfers to you. We are happy to put this in writing up front.
First of all, we adapt to whatever stack you are already on. We would rather fit your codebase than ask you to fit ours. When we get to choose, we reach for TypeScript, Go, Rust, reactive Java, Kotlin, and Dart / Flutter, usually with PostgreSQL for storage. Services talk over REST, or Protocol Buffers and gRPC where it helps. On the front end, Svelte, React, Astro, or Vue. For infrastructure, Terraform and AWS CDK with containers, on bare metal, Hetzner, AWS, Google Cloud, or Cloudflare. We keep up with the field and will pick the newest tools when they earn it, but only the stable ones, so you are not left on something that breaks or disappears.
No. LASIKUU is a focused, independent studio. You work directly with the people building your product, and we take on a deliberate number of projects at once so each one gets real attention.
Tell us what you are working on. A short message is enough; we will reply with honest next steps.
