Discuss your project

Our approach

How we run projects

The best way to judge a software partner is to see, up front, how they run a project. Every step has a duration, an owner and a written deliverable.

Way of working

Five steps, each with a written deliverable

  1. Discovery

    1 call + 2–3 days

    We map the current process, the roles and the exceptions over a video call. The output is yours even if you do not accept the proposal.

    Deliverable: process map and problem statement

    Free

  2. Proposal

    2–3 days

    Scope, timeline, price and what is out of scope are put in writing.

    Deliverable: fixed-scope proposal and schedule

  3. Development

    Depends on scope

    A usable release every week, so changes are made while they are still cheap.

    Deliverable: a working release every week

  4. Handover

    1 week

    Go-live, data migration and team training.

    Deliverable: source code and access in your hands

  5. Maintenance

    Monthly

    Monitoring, updates and new development. If you want to hand the system over to another team, the handover document is ready.

    Deliverable: monthly report and uptime figure

    Optional

Quality assurance

Every change that goes live passes the same quality gates

We use AI tools in development because they make us faster. Quality is enforced by automated tests, security checks and an engineer's sign-off.

  1. Specification

    Written acceptance criteria

  2. Development

    Engineers and AI tools

  3. Automated tests

    Unit and end-to-end tests

  4. Security

    Permission tests and vulnerability scans

  5. Review

    Code review and approval

  6. Release and monitoring

    Post-release monitoring

Principles

Four commitments that hold on every project

Scope is in writing

The proposal states what is out of scope as clearly as what will be done. That prevents most surprises before work begins.

You own the result

Source code, infrastructure access and documentation are handed over to you on delivery. You are not tied to us for maintenance.

Quality is measured

Test results and before-and-after screenshots of every screen change are shared with each delivery.

AI is supervised

Every AI action that changes a record asks for approval; when the AI is not sure, the case goes to a person.

Questions

How does a custom software project start?

With a free discovery call. We work out together how things run today, then send you the scope, timeline and price as a written proposal. On delivery, the source code and infrastructure stay with you.

We are not in Türkiye. How do we work together?

Remotely, in English. Discovery and weekly reviews happen over video calls, every release is a link you can open, and the contract is with Eymence LLC, a US company.

Who owns the code?

You do. The source code, the infrastructure accounts and the documentation are handed over on delivery, and maintenance with us is optional.

Let's start with a discovery call

We map your current process with you, then tell you in writing where software will add the most value.

Discuss your project