# Sample documents: see the format before you send a brief

URL: https://fincodelabs.com/en/samples · Publisher: Fincode (Fincode Yazılım ve Teknoloji A.Ş.), Istanbul, Turkey · Updated: 2026-11-06

Fincode has no client references to show you, so these pages show what the documents look like instead: a scope document, a proposal, a test report and a code review report. They are samples of the format, not a real client and not real trading results. The scope and the proposal are written for a fictional project. The test report and the code review report come from runs of code Fincode published, which you can repeat.

## Four samples, one template and one checklist

- [Sample scope document](https://fincodelabs.com/en/samples/scope-document): Testable requirements for a fictional order service, with failure behavior, acceptance checks and what is out of scope.
- [Sample proposal](https://fincodelabs.com/en/samples/proposal): Milestones, approvals, assumptions and delivery risks. Cost, dates and contract terms appear as placeholders.
- [Sample test report](https://fincodelabs.com/en/samples/test-report): A real run of Fincode's published reference code against its own mock exchange: failure cases, test names, log excerpts and what was not run. No profit figures.
- [Sample code review report](https://fincodelabs.com/en/samples/code-review-report): Fourteen defects in a fictional bot written wrong on purpose, ranked by priority, each reproduced by a script you can run.
- [Rule document template](https://fincodelabs.com/en/samples/rule-document-template): A blank form for your own written rules. It holds no suggested rule or parameter.
- [Exchange API integration checklist](https://fincodelabs.com/en/exchange-api-integration-checklist): Permissions, signing, clock sync, rate limits, client order IDs, retries, partial fills, reconciliation, restarts, logging and go-live.

## How the documents map to a project

Every project runs in [four stages](https://fincodelabs.com/en/how-we-work), and each stage ends with something you can read or run. You write your rules, with the template if it helps. Discovery ends with a scope document. The proposal turns that scope into work items, dates and cost. Development and testing end with a test report, which you read before anything goes live.

The code review report belongs to a [separate service](https://fincodelabs.com/en/services/trading-bot-code-review), for code you already have. The checklist is for anyone building or checking an exchange integration, with or without Fincode.

### What these samples can and cannot tell you

They show how work is specified, tested and reported, so you can judge the depth before you commit to anything. They are not a record of delivered client work. The two reports are runs of the [order gateway reference](https://fincodelabs.com/en/reference/order-gateway) and of a demo bot in the same download, and you can repeat both. Fincode's own product is the [Fiva iPhone app](https://fincodelabs.com/en/fiva), which shows fund data and estimates and does not place trades, so it is not evidence of order handling either.

When you are ready, [send a short brief](https://fincodelabs.com/en/contact). You do not need to share your rules yet.

### What a sample is not

- A real client: Client A, Exchange A and Bot A are fictional
- Client results: numbers in the scope and the proposal are illustrative, and the reports come from Fincode's own published code
- Evidence of profit: no sample holds a return, a win rate or a backtest result
- Rules or settings to copy: limits and thresholds stay blank for the customer to set

## Questions about the samples

### Are these real client documents?

No. Client A, Exchange A and Bot A are fictional, and the numbers in the scope document and the proposal are illustrative. The test report and the code review report come from real runs of code Fincode published, so you can repeat them, but neither is client work. Fincode has no client references to show.

### Why publish samples instead of case studies?

A case study needs a client. A sample needs none, and it still lets you judge how requirements are written, what gets tested and how failures are reported, before you send anything.

### Would my documents look like this?

The structure follows these samples. The content comes from your project, your rules and your platform, and the terms shown here as placeholders are set in your own proposal and contract.

### Can I use the template and the checklist without hiring Fincode?

Yes. You can fill in the template and work through the checklist with any developer. Both are free to read on this site, with no form to fill in.

### Do I need to share my rules to get a reply?

No. Your first message only needs the platform, what the software should do and your timeline. Written rules come in during discovery, because the scope depends on them.

---

Published by Fincode (Fincode Yazılım ve Teknoloji A.Ş.), a software company in Istanbul, Turkey: https://fincodelabs.com/en/samples