What FieldKo does today: FieldKo records what field teams did and saw, as Salesforce records. Sales, margin, inventory, and cost data come from other systems. Estimating commercial impact or return on investment (ROI) always needs that external data.
What Good Looks Like
- Results are reported on a ladder, from effort to net contribution, and each step is labeled.
- Commercial claims use a comparison group, not only before and after.
- Costs include field time, travel, materials, management time, and rework.
- Operational gains, such as better availability, are reported as operational gains, not dressed up as revenue.
- Assumptions and limitations are written down next to the result.
When to Use It and Common Failure Patterns
Use this page for a pilot review, a budget case, or a quarterly business review where someone asks what the field program is worth. Common failure patterns:- More visits called ROI. Activity goes up, and it’s reported as value.
- Before and after only. A seasonal lift is credited to the field team.
- Reverse cause. A promotion that sells well also draws more visits, so visits look like they caused the sales.
- Missing costs. Only field wages are counted.
- Changed definitions. A survey or scoring change makes the “after” period look better.
Operating Procedure
Report on a Measurement Ladder
Each level is context for the next, but doesn’t prove it.
Choose a Fair Comparison
- Pick a group of stores that gets the change and a similar group that doesn’t, over the same period.
- Match or adjust for past sales, store format, season, promotions, price, stock, and local demand.
- If you can assign stores to the groups at random, do.
- If you can’t, write down the assumptions behind the comparison.
Count the Costs
Include field labor and travel, materials, management time, services, and rework caused by the change. Keep fixed and variable costs separate, so you can see what scaling would cost.Calculate and Document
- Incremental units: the difference against the comparison group, not before versus after.
- Incremental contribution: incremental units × contribution margin per unit.
- Net contribution: incremental contribution − incremental cost.
- ROI: net contribution ÷ incremental cost, when the cost is positive.
How to Implement It in FieldKo
To set up a comparison and join the data:
- Define the groups. Save the test stores and the comparison stores as account sets, and run the change as a field campaign on the test set. See Run Field Campaigns.
- Report the FieldKo side. Build reports for levels 1 to 3 by account, using Retail Execution Metrics and Trend Reports Over Time.
- Bring in sales data. Either load sales and margin data into your org as your own object linked to the account, or export FieldKo data to the tool that holds sales data. Join on a stable store key, such as your enterprise resource planning (ERP) account number. See Export FieldKo Data and Photos and Integrate FieldKo with Other Systems.
- Freeze the definitions. Don’t change survey questions or scoring during the measurement period. See Keep Questions Consistent.
Fictional Example
Fictional example: a made-up juice brand, Coral Bay Juices, adds a weekly display check in 30 test stores for 8 weeks. Thirty matched stores keep the normal call plan.
Without the change, the test stores would be expected to grow like the comparison stores: 10,000 × 1.13 = 11,300 units. Incremental units are 12,400 − 11,300 = 1,100. At a contribution margin of $2.50 per unit, incremental contribution is $2,750. Incremental cost is 60 extra field hours at $30 ($1,800) plus $400 of display materials, so $2,200. Net contribution is $2,750 − $2,200 = $550, and ROI is $550 ÷ $2,200 = 25%. This is a teaching example, not a benchmark.
What to Measure
What to Do When It Goes Wrong
Checklist
- Write the business problem, the change, and the primary outcome.
- Choose test and comparison stores, and save them as account sets.
- List possible confounders: season, stock, price, promotions, retailer events.
- Freeze survey and metric definitions for the period.
- Agree where sales, margin, and cost data come from, and the store key to join on.
- Calculate each ladder level, and document the assumptions.