SERVICES & PROCESS

What we build,
and how we build it.

We build web applications, business systems and AI features. The same small team stays on a project from the first meeting through launch and maintenance.

01 — SERVICES

What we do

The areas we take on, with typical timelines. Actual schedule and cost are estimated for each project after the first meeting.

01

Web applications

Products people log in to: member sites, booking and payment flows, admin panels and dashboards. Screens are designed in Figma with our partner studio Piyetra before any code is written.

Typical work
  • SaaS and member sites
  • E-commerce and booking
  • Admin panels and dashboards
Timeline
2–4 months (a first release in about 6 weeks)
Stack
Laravel, JavaScript, Node.js, MongoDB, Figma
Related work
Intellio Dashboard, Diamond Marketplace

02

AI & machine learning

AI for one specific job: searching internal documents, answering routine questions, classifying images or behavioural data. We start with a short proof of concept on your real data, and build the production version only if the accuracy is good enough to use.

Typical work
  • Internal document search (RAG)
  • Support chatbots
  • Image and behavioural data classification
Timeline
Proof of concept: 3–5 weeks
Stack
Python, PyTorch, TensorFlow, LLM API
Related work
Puddin.ai

03

Business systems & APIs

Software for the parts of your business that packaged tools don’t fit: work still done in spreadsheets and on paper, systems that need to exchange data, control software for dedicated hardware.

Typical work
  • Inventory and order management
  • API integrations between services
  • Device control and desktop software
Timeline
1.5–4 months
Stack
Java, REST API, MongoDB
Related work
Reveal Diamond Detector

04

Maintenance & improvements

Server monitoring, security updates and small changes after launch, on a monthly contract. We also take over systems built by other companies, once we have read through the code.

Typical work
  • Monitoring and incident response
  • Framework and OS updates
  • Small features and fixes each month
Timeline
Monthly, ongoing

02 — PROCESS

How a project runs

Most projects go through these seven steps. On smaller jobs, some of them are merged.

Typical time from first contact to launch

1.5–4 months

PHASE 01

Before the contract

Free of charge
  1. Get in touch

    Send the form or an email. A rough idea is enough; we will ask about the rest.

    Duration
    Reply within 2 business days
  2. First meeting

    About an hour online on your goals, current setup, budget and timing. We can sign an NDA beforehand.

    Duration
    About 1 hour
  3. Proposal and estimate

    A document with the feature list, schedule, team and price.

    Duration
    About 1 week
    Deliverables
    Proposal and quotation
PHASE 02

Design and build

  1. Requirements and design

    We draw the screens in Figma and settle the spec while clicking through the real flows with you. What we agree on here is what gets built.

    Duration
    1–3 weeks
    Deliverables
    Screen designs (Figma) and requirements document
  2. Development

    The test environment is updated every two weeks, so you see working software early and can reorder priorities along the way.

    Duration
    3 weeks–2.5 months
    Deliverables
    Test environment
  3. Testing and launch

    You run acceptance tests, and once they pass we go live. Bug fixes during the first month after launch are included.

    Duration
    1–2 weeks
    Deliverables
    Production release and full source code
PHASE 03

After going live

  1. Maintenance

    Move to a monthly maintenance contract, or end the project here.

    Duration
    Optional

03 — ENGAGEMENT

Contracts and team

For a clear scope

Fixed price

Scope and price are agreed up front, and we are responsible for delivering what was agreed.

For changing requirements

Monthly team

You reserve engineering time by the month. Suits new products and ongoing development, where priorities shift.

After launch

Maintenance contract

Monitoring, updates and small changes for a fixed monthly fee.

Team
1–7 senior software engineers and a design team
Languages
Japanese, English
Meetings
Weekly, online, 30 minutes
Tools
Slack, Chatwork, Microsoft Teams or email
Office
Shinmachi, Osaka (in-person meetings within Kansai)

04 — FAQ

Frequently asked questions

Q. Can we ask for something small?
A.

Yes. Adding one feature to an existing site, or only an AI proof of concept, is fine.

Q. We don’t have a budget yet.
A.

That is not a problem. We give you a rough figure after the first meeting, and can suggest a smaller first release that fits your budget.

Q. Can you take over a system another company built?
A.

We decide after reading the source code and checking the servers. Sometimes we will tell you that rebuilding costs less than patching.

Q. Who owns the source code?
A.

Copyright passes to you once the final payment is made. If you need a different arrangement, we set it in the contract.

Q. Do you work with companies outside Japan?
A.

Yes. We work in English, and several of our clients are based in Turkey.

WORK WITH US

Tell us what you have in mind.

No brief or spec needed. A few lines about what isn’t working today is enough to start.

Contact us

CONTACT

Contact us

  1. 1 Details
  2. 2 Review
  3. 3 Done

Inquiry type Required

We use the personal information you enter only to reply to your inquiry, and never share it with third parties without your consent.