We build a system that runs the work of your field reps from a phone: route and visit plans, mobile ordering, in-field collections, shelf and competitor photos and target tracking all come together in a single app. The app also works without an internet connection and synchronises by itself once the connection returns.
In field sales, most of the day is spent where the office cannot see it. The rep sets off in the morning; spends the day calling on corner shops, supermarkets, stationers or restaurants, writes the order in a notepad, collects payment, issues a receipt by hand, returns to the office in the evening and enters the same information into the system a second time. That second entry both takes time and produces errors; some orders slip to the next day, some payments are posted late, and the customer balance runs a day behind the real position. At month end, when someone asks how many times a given outlet was visited, which customer has not been seen for a long time, or which product is genuinely not moving in the field, there is no solid record to hand.
The need here is not the same as the classic customer management need, and it is worth drawing the line. CRM is set up for a small number of long-cycle opportunities: samples, quotes, revisions, proformas and follow-up spread over months. Sales force automation, by contrast, is set up for high-frequency visits in large numbers; the same customer is called on several times a month, an order and a payment are taken at every visit, and the whole job is handled on a phone and usually standing up. One manages the persuasion process of selling, the other the repeating operation of selling. The two structures can also live side by side in the same company; in that case the customer record is held in common and both systems look at the same account data.
In the application we build, the rep's day starts with a plan: which outlets are to be visited today, in what order, and what is waiting at each customer. When a visit is opened, the customer's balance, past orders and any overdue invoices are on screen; the order is entered with current prices and discount rules, and warehouse stock is visible. The payment is recorded, the receipt is produced from the phone and closed with the customer's signature. Shelf layout, display and competitor prices are documented with photographs. The result field cannot be left empty when the visit is closed; if no order was taken, the reason is flagged from a list. The order reaches head office instantly, dispatch can begin before the day is out, and the rep no longer has to call in at the office in the evening to enter the same data a second time.
We want to be clear on two points. First, offline working is a requirement of this job, but it is not magic: the app holds an order entered without a connection on the device and synchronises it when the connection returns; on the other hand, the stock and balance seen at that moment are the last information held on the device, so, rarely, there can be a clash over the same stock. Rather than hide that, we build a design that catches the conflict and tells the user about it. Second, location data. Location can be used as visit evidence and for route tracking; but that does not mean the employee is under continuous surveillance. We tie location to the moment of the visit, we do not collect it outside working hours, and we set up the personal data processing framework together with your obligations under KVKK (Turkish data protection law).
Businesses that call regularly on large numbers of outlets in areas such as food, drinks, cleaning products and stationery. The real issue here is not winning one large order but collecting hundreds of small ones without errors, on the same day and at the right price. The margin for error looks small, but it adds up by the end of the day.
Manufacturers who visit dealers and retailers with their own field team. When there is no record of whether the visit actually happened, which product was discussed and what the customer said, field management rests entirely on word of mouth. When a representative leaves, the history of the territory goes with them and the new arrival starts from scratch.
Teams that carry the product in the vehicle and deliver on the spot. The most critical points of this model are that vehicle stock is accurate at any moment, that goods sold and goods taken back are deducted at the same time, and that the end-of-day vehicle reconciliation balances. When it runs on paper, the gap grows a little wider every day.
Companies where a significant share of cash and cheque collection happens in the field. Where receipts are written by hand and payments are posted the next day, end-of-day reconciliation becomes harder and overdue balances cannot be tracked in real time. The conversation about payment held with the customer also rests on memory rather than data.
Sales outlets are attached to routes by territory, visit frequency and priority; the daily visit list arrives on the rep's phone by itself every morning. Unplanned visits can also be recorded, but they are flagged separately. That way, how often each outlet is visited, which customer has been skipped for a long time and how closely the route is actually followed can all be read from a list.
A visit is opened, the steps are completed in order, and the result is recorded at closing: order taken, payment collected, customer absent, no order placed. Empty visits with no stated reason become visible. Location and a time stamp can be attached to the visit record; this data is held only as evidence tied to the moment of the visit, not as a continuous trail.
The order is entered in front of the customer by scanning the product barcode; the current price list, customer-specific discounts and campaign rules are applied automatically, which reduces the risk of the wrong price. Because warehouse stock is visible, an order that cannot be fulfilled is not taken in the first place and no promise is made to the customer that cannot be kept. The order reaches head office instantly and dispatch can start the same day.
Cash, cheque and promissory note collections are recorded during the visit; the receipt is produced from the phone, the customer signs on screen and the record closes at the same moment. The rep sees the customer's balance and overdue invoices on the visit screen, so the conversation about payment is based on data rather than memory. End-of-day cash and vehicle reconciliation is also drawn from the same records.
Shelf layout, display positions, out-of-stock situations and competitor price labels are documented with photographs; the photographs are archived against the visit, the customer and the date. The head office team sees the field as it is and in date order, not as it is described. Whether campaign and display agreements have actually been implemented is also verified from this record, leaving no room for argument.
Targets are defined by turnover, product group, new customers or number of visits; the rep sees their own achievement during the day. Because commission is calculated from the same data, month-end corrections and disputes fall away. The field team knows how far it is from target before the month ends; the area manager can also step in without leaving it too late.
The app also works without an internet connection; visits, orders, collections and photographs are held securely on the device and synchronised in the order they were entered once a connection returns. Sync status is shown clearly to the user; the number of pending records stays on screen and nothing is lost silently. Records that clash are not overwritten; they are flagged and passed to the right person for a decision.
We do not settle for hearing about the process in the office. We spend a full day out with a field representative; we see on the spot how the order is taken, how payment is collected, at which point the phone cannot be used, and which information is entered a second time in the evening. The number of screens in the app, the order of the flow and which fields will be mandatory are decided from that observation.
The outlet list is cleaned, duplicate records are merged, and territories and visit frequencies are defined. Price lists, discount and campaign rules are put in writing. If this step is skipped, the field team meets wrong prices and missing customers on day one, and trust in the app is broken in the first week.
Visit, order and collection flows are developed; the interface is simplified so it can be used one-handed and standing up. Offline scenarios are tried under real conditions: indoor areas, weak signal, a full day without a connection and a bulk sync in the evening. How the system will behave in the event of a conflict is also decided here and put in writing.
A connection is made to your existing ERP or accounting package for account, stock, price and invoice flows; orders and payments coming in from the field are transferred to the central system. Which data flows in which direction, which system is the master source and what happens in the event of an error are fixed in writing.
We go live first with a single territory and a limited number of representatives; the old method runs in parallel for the first period. The flow is simplified with the feedback that comes back, and it is then rolled out across the whole field. Maintenance and support continue after go-live; the source code, the database and the documentation are handed over to you.
The intensity of use and the length of the cycle differ. CRM is set up for a small number of opportunities that stretch over months: samples, quotes, revisions, proformas. Sales force automation is set up for large numbers of repeating visits; the same customer is called on several times a month and an order and a payment are taken each time. The two do not clash and can be used together in the same company. In that case the customer record is held in common and both systems look at the same account data.
Yes, offline working is a requirement of this job. Visits, orders, collections and photographs are stored on the device; when a connection returns they are synchronised in order and the sync status is shown clearly to the user. There is a limit to this: the stock and balance you see while offline are the last information held on the device. Rarely, there can be a clash over the same stock. Rather than hide that possibility, we build a design that catches the conflict, does not silently overwrite the record and notifies the right person.
In the setup we recommend, no. We use location not as a continuous trail but as evidence tied to the moment a visit is opened and closed; we do not collect location outside working hours and we limit how long the data is retained. This is a personal data processing activity: the privacy notice, the retention period and access rights must be defined from the outset. The obligation rests with you as the employer; we build the system so that it fits that framework and handle the KVKK (Turkish data protection law) side together with the relevant module.
Both can be built, but the flows differ. In pre-sales the rep collects the order and delivery follows later; what matters there is order accuracy and the delivery plan. In van sales the product is in the vehicle and is delivered on the spot; there, the accuracy of vehicle stock at any moment, processing returned goods at the same time and the end-of-day vehicle reconciliation are decisive. We clarify which one you use during discovery, and for companies running both models we build separate flows.
We do not promise that, and we would advise you to treat any proposal that gives you a figure with caution. What the software does is make the work visible and reduce repeated effort: was the visit actually made, which outlet was skipped, how many hours did it take for the order to reach head office, when was the payment posted. Any increase in sales depends on the decisions taken with that visibility. The concrete, measurable gain is that double data entry disappears and the order enters processing the same day.
A mobile app for the field team that works offline; customer outlets, routes and visit plans; visit evidence and result records; mobile ordering with current prices and discount rules; in-field collections and mobile receipts; a shelf and competitor photograph archive; target and commission tracking; ERP or accounting integration; field and territory reports. The source code, the database and the documentation belong to you.
In a 30-minute discovery call we listen to what you need and tell you honestly whether custom development or an off-the-shelf product is the better answer.
We unify the customer data held on your website, e-commerce platform, CRM, call records and in-store tills under a single identity. Duplicate records are matched, segments are generated by rule, consent status travels with every record, and segments are pushed to channels in a controlled way. The aim is not another report, but a working customer view that the channels can use every day.
Details →We turn email, SMS and WhatsApp messages from announcements sent one at a time into flows that run themselves according to what the customer does. Abandoned basket, welcome, win-back and post-purchase flows are built; people who show interest are scored and handed over to the sales team. Consent and sending discipline are built into the flow itself.
Details →We build a learning management system (LMS) that brings together, in one place, the training catalogue, who is required to take which course, who has completed it and when a certificate expires. When an audit asks for the record of your health and safety and quality training, it comes out on a single screen rather than after hours of searching.
Details →We build a system that ties the company goal to team and individual goals and bases the end-of-period review on records rather than memory. Goal management runs on OKR and individual assessment on a performance management system (PMS); we keep the two side by side on the same platform without mixing them up.
Details →We do not replace Logo, Mikro or Netsis (the accounting packages in common use in Türkiye). We build a finance layer that gathers current accounts, banks, cash, cheques and promissory notes, expenses and cash flow alongside your accounting package, and puts collection, payment and approval processes on rules. The record is still kept in accounting; visibility and process run in this layer.
Details →We move the budget out of Excel files and into a system that is versioned, has a named owner and is compared with actuals automatically. When the month closes, the variance report is not put together by hand; the reason for the variance is recorded, the forecast is updated and the management pack is produced from the same numbers. The goal is not more reports, but seeing where you stand against target in a single figure nobody disputes.
Details →
