Data Strategy & Platforms
A data platform is only as reliable as its definitions. We agree what revenue, margin and a customer mean before we move a single table.
Questions we help answer
- Why does every team have its own version of revenue, and which one should the board use?
- Do we need a data warehouse, or would cleaner source data and a few reconciled reports do the job?
- Which of our data do we hold ourselves, and which sits only inside a vendor platform we could lose access to?
- How do we combine store, marketplace, advertising and accounting data without counting the same sale twice?
- How much does our consent banner remove from analytics, and how do we report around it honestly?
What we do
Metric dictionary
Written definitions for revenue, gross margin, contribution, customer acquisition cost and the other figures leadership uses, each with its source system and calculation.
Event and tracking design
Event specifications, server-side tracking and consent handling for websites and apps, checked against recorded orders before sign-off.
Pipelines and warehousing
Extraction from commerce, advertising, CRM and accounting systems into a warehouse or a simpler shared store sized to the volume, with scheduled loads and failure alerts.
Data quality controls
Uniqueness, completeness and range checks on the fields that act as keys between systems, such as SKUs, customer IDs and order numbers.
Data ownership register
A list of the data held only in third-party platforms, with its export route and retention period, and what the business would lose if an account closed.
- How an engagement with THEFOCUS startsDiscuss this with us
How we approach it
- 01
Definitions before tables
Each leadership metric is defined once, in writing, with its source named. Reports that use a different definition say so on the page.
- 02
Reconcile at every load
Each load is compared with the source total. A load that does not reconcile stops and raises an alert instead of feeding a report.
- 03
Prove the key
Before a field joins two systems we test that it identifies exactly one record. SKUs reused across products and customers split across several email addresses surface at this step.
- 04
Size the platform to the business
A business with thousands of orders a month needs a different stack from one with millions. We size the platform to the data volume and to the team that will run it.
Client results
View allTürkiye · Real Estate & Property Development · 2026
Listing platform prototype and build specification for a cross-border property agency
A licensed property agency selling homes and investment property in several countries wanted one platform for its own stock, partner listings and new developments. We built a clickable prototype, a headless storefront build and a written specification for the full listing and enquiry platform.
Prototype and specification delivered on staging; platform not yet in production
Türkiye · Jewellery & Luxury Goods · 2026
Launch program for a new fine jewellery brand, from positioning to storefront and production equipment
A young jewellery brand preparing to sell direct to consumers engaged us for a multi-phase launch program. So far that has produced the brand position, a built storefront, the sales and social accounts, a product render standard and a purchase recommendation for in-house casting equipment.
Positioning, storefront and equipment decision delivered; brand not yet launched
Türkiye · Retail & E-commerce · 2025‑2026
Audit, measurement repair and paid media relaunch for a design-objects online brand
An online brand selling high-ticket decorative design objects commissioned an audit and put it through an independent quality review. It then had us carry out the findings one ticket at a time and relaunch its search and social advertising.
Fixes verified in production; paid relaunch results not yet measured
Relevant industries
How an engagement with THEFOCUS starts
A first conversation is about your situation. If there is a fit, we propose a scoped diagnostic with a fixed deliverable before any larger commitment.
Discuss this with us01
A working conversation
Forty-five minutes with the person who would lead the work. We ask about the decision, the systems behind it and the deadline.
02
A scoped diagnostic
Read-only access, a fixed timeframe and a written finding: what the records show, what it costs and what to change first.
03
A plan you can act on
Changes, owners, measures and exclusions in writing. The same team then builds and measures, or hands over cleanly.
- One accountable team
- The people who diagnose also build the systems and measure the result.
- Partners chosen per problem
- Independent specialists join for the parts that need them, under one contract.
- Records before dashboards
- Orders, ledgers and logs are reconciled before any recommendation depends on them.
Questions executives ask
Do we need a data warehouse?
Not always. When the volume is modest and the sources are few, reconciled exports and a well-defined reporting model often answer the same questions at lower running cost. We recommend a warehouse when the number of sources or the volume makes the simpler route fragile.
How do you deal with data lost to consent choices?
We measure the share of activity the consent setup removes, keep ratios that remain valid, and use the commerce platform's order count as the reference figure. Server-side collection is only configured within the consent and legal basis your advisers have approved.
Discuss this with us
A few details help us route your enquiry to the right partner. Fields marked optional can be left blank.