The balance question gets put to whoever is teaching. How do you take it off the floor?

The moment you stop keeping the balance in a list of its own, the question moves too. In Pilatesco what is left sits on the customer's record, drops when a booking is written, and moves by rule when the state changes. Nobody is asked; the record is read.

Does someone who never turns up count the same as someone who cancels in advance?

No. The two write different results to the balance. Which state gives the right back is set in a rule beforehand rather than in a conversation at the door, and when the rule changes it changes in one place instead of being remembered customer by customer.

We have two locations and want one package to work at both. Can you do that?

Pilatesco was written for a single business, and sharing a balance across locations was never tried there, so we have nothing to show. That scope can be discussed, but we cannot promise it on the strength of existing work.

Payment lands weeks before the service is delivered. Where does that gap sit?

We promise no accounting integration on this page; what we describe is the shape of the record. Selling happens once, use spreads over weeks, and both stay on one customer record, so the part paid for and not yet taken is read rather than estimated.

Process Tracking · Sisli

Process Tracking for Sisli businesses

A package is sold in one movement and then drains away over weeks. The sale looks closed while the work is not: what remains is an open commitment, and the calendar says nothing about where it stands. In a session studio around Tesvikiye in Sisli that question can come up several times a day. Pilatesco ties the answer to the balance itself. Writing a booking into the calendar takes one session right off the package, and the number left sits on the customer's record.

Get a quote Tell us about your project

Process Tracking — Sisli

Sisli's texture is the Nisantasi cosmetics trade and the central commerce around it, with care and session studios finding room on the same streets. If what you sell never rests on a shelf, process tracking software for Sisli means following rights already paid for but not yet taken, rather than keeping an appointment book. The work closest to this district's business texture is Pilatesco. One thing it cannot show: it was written for a single business, and making one package valid across several locations was never tried there. It runs on Laravel and MySQL. No team of ours turns up at the studio; we work remotely.

The state of a right is read from the balance: bought, reserved, used or given back, with all four accumulating on one customer record.
A cancellation, a no-show and a completed session write different results to that balance, and which of them returns the right is settled in a rule rather than at the start of a session.
Selling happens once while use spreads over weeks, and because both meet on the same customer record, what a business still owes is read in one place.

Why Algoriel

Keeps working offline

The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.
Entry from QR and location

Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.
Records land the same hour

Jobs close in the field, so the office sees where each one stands without waiting for end of day.
Office and field read one source

The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What the record attaches to

Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.
The entry that stays open

Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.
Who was where, on the record

Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.
What is left when the figure is disputed

Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.
Records taken beyond coverage

In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.
Process rules kept out of the code

Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

Pilatesco — the balance is the state, a booking is what moves it

A customer buys a package and it sits on their own record rather than in a ledger kept beside it. Writing a booking into the calendar takes one session right off that package, and where the process stands is read from what is left. A cancellation, a no-show and a completed session each move the balance differently, and which of them gives the right back is written into a rule beforehand. The sale happens once while use spreads over weeks, and because both meet on one record, rights paid for but not yet taken stay visible. The system runs on Laravel and MySQL.

Read the case study →

Working with Sisli teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

The first release ships as a working piece; extras follow later.
Every client we know of is in Turkey.
Decisions stay in writing; progress shows in working screens.

Frequently asked

The balance question gets put to whoever is teaching. How do you take it off the floor?

The moment you stop keeping the balance in a list of its own, the question moves too. In Pilatesco what is left sits on the customer's record, drops when a booking is written, and moves by rule when the state changes. Nobody is asked; the record is read.
Does someone who never turns up count the same as someone who cancels in advance?

No. The two write different results to the balance. Which state gives the right back is set in a rule beforehand rather than in a conversation at the door, and when the rule changes it changes in one place instead of being remembered customer by customer.
We have two locations and want one package to work at both. Can you do that?

Pilatesco was written for a single business, and sharing a balance across locations was never tried there, so we have nothing to show. That scope can be discussed, but we cannot promise it on the strength of existing work.
Payment lands weeks before the service is delivered. Where does that gap sit?

We promise no accounting integration on this page; what we describe is the shape of the record. Selling happens once, use spreads over weeks, and both stay on one customer record, so the part paid for and not yet taken is read rather than estimated.

Process Tracking in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service

Process Tracking for Sisli businesses

Process Tracking — Sisli

Why Algoriel

Keeps working offline

Entry from QR and location

Records land the same hour

Office and field read one source

What we build

What the record attaches to

The entry that stays open

Who was where, on the record

What is left when the figure is disputed

Records taken beyond coverage

Process rules kept out of the code

Work like this

Pilatesco — the balance is the state, a booking is what moves it

Working with Sisli teams, remotely

Frequently asked

The balance question gets put to whoever is teaching. How do you take it off the floor?

Does someone who never turns up count the same as someone who cancels in advance?

We have two locations and want one package to work at both. Can you do that?

Payment lands weeks before the service is delivered. Where does that gap sit?

Process Tracking in other cities

Ankara

Istanbul

Izmir

What stands behind your month-end figure today?

Process Tracking for Sisli businesses

Process Tracking — Sisli

Why Algoriel

Keeps working offline

Entry from QR and location

Records land the same hour

Office and field read one source

What we build

What the record attaches to

The entry that stays open

Who was where, on the record

What is left when the figure is disputed

Records taken beyond coverage

Process rules kept out of the code

Work like this

Pilatesco — the balance is the state, a booking is what moves it

Working with Sisli teams, remotely

Frequently asked

The balance question gets put to whoever is teaching. How do you take it off the floor?

Does someone who never turns up count the same as someone who cancels in advance?

We have two locations and want one package to work at both. Can you do that?

Payment lands weeks before the service is delivered. Where does that gap sit?

Process Tracking in other cities

Ankara →

Istanbul →

Izmir →

What stands behind your month-end figure today?

Ankara

Istanbul

Izmir