anotherdevstudio
Book a call

One system, and everyone sees only what they should

I build internal systems for companies with departments. We start with a pilot in one team. Your IT sees everything from day one, and the rest of the company moves over only once the pilot works.

Book a call→

The first call is free. Feel free to bring someone from IT.

01 The cost

What it’s costing you today

In a larger company, a new system rarely fails because of the tech. It fails because of everything around it.

  • 1Shadow tools
    Every department has its own spreadsheet and its own account in some app.
  • 2One big-bang rollout
    Six months of work, and then it turns out people work differently.
  • 3A system nobody else can take over
    One vendor knows everything, and only they can change anything.
02 Stages

One team first, then the whole company

The pilot is small and has success criteria we check at handoff. If it doesn’t meet them, we stop there, and you keep the code and what we learned.

03 Access

Who sees what, and who changed what

  • Roles and permissionsWe set them up together: by department, team or individual.
  • Company sign-inPeople sign in with the company account they already use, with 2FA.
  • Audit logEvery change has an author and a timestamp. You can see who granted access, who revoked it and who downloaded a report.
  • Data in the EUServers in the EU or your own infrastructure. The data belongs to the company.
04 For your IT team

What the person who signs off gets

  • Access to the repository from week one, not just at handoff.
  • A write-up of the architecture, data and access to review before rollout.
  • Integration with the systems you already have, through their APIs.
  • Documentation for users and for whoever will maintain the system.
  • A handoff session where I walk you through everything under the hood.
05 Steps

How I work

  1. Step 1

    A call

    Thirty minutes about what needs to change and who makes the call. Free.

  2. Step 2

    Discovery

    I talk to the pilot team and your IT. The result is a plan, the pilot’s success criteria and a fixed price.

  3. Step 3

    The pilot

    One team works in the system. A first preview usually in a week.

  4. Step 4

    Rollout

    More departments, access, training, documentation. A separate plan and a separate quote.

  5. Step 5

    Support

    A support agreement: fixes, new features and response times, in writing.

06 Tools

What I connect it to

07 Next

See also

08 Pricing

How billing works

I give you the number after discovery, in the plan. I won’t guess at it on the first call.

  • The pilot at a fixed priceAfter discovery you get a pilot plan and one price. It doesn’t creep up along the way.
  • Rollout priced separatelyI quote it after the pilot, once we know what works. No commitments in advance.
  • Support by the hourFixes and new features after rollout are billed hourly under a support agreement.

Hosting in the EU or on your side. The code, documentation and access are yours.

Tell me what needs to change, and you’ll get the number in the plan. Book a call→

09 Straight talk

When you don’t need me

  • 1An off-the-shelf system does what you want, and the team will adopt it. I’ll tell you which one.
  • 2You’re looking for a vendor with a team of dozens on a multi-year contract.
  • 3Nobody in the company owns this project.

Not sure it’s a fit? Ask me on a call and I’ll tell you straight. Book a call→

10 FAQ

Questions

You’re one person. What about the risk?

That’s why we start with a pilot, and your IT has the code and docs from the start. The system doesn’t depend on me: any developer who knows TypeScript can take it over.

Can our IT team review it?

Yes. They get repository access from week one, and a review before rollout is part of the plan.

Will it connect to our systems?

Usually, yes, through their APIs or file exports. I check that during discovery, before I give you a price.

Where does the data live?

On servers in the EU or on your own infrastructure. It belongs to the company.

Will you sign an NDA and a data processing agreement?

Yes, before discovery.

What happens after rollout?

A support agreement with response times in writing. I reply the same business day (Polish time, CET).

11 Call

Let’s talk

Pick a time. Come on your own or bring someone from IT. I reply the same business day (Polish time, CET).

Pick a day

Time zone: Europe/Warsaw