--- title: "Send Us One Report, Get a Written Plan | Project2100" description: "Describe one report your team rebuilds every week or month. An engineer replies with a free written plan for automating it." url: https://www.project2100.com/report-review updated: 2026-10-23 generated: true --- > The machine-readable version of https://www.project2100.com/report-review > > The body below is this page's own content, generated from the page at build time: the same words, in the same order, with nothing summarised or reworded. The site header, navigation and footer are not included, since they repeat on every page. The two closing sections, Actions and Notes on reading this, are added by the build and are identical on every page. [Project2100](/index.md)[Back to site](/index.md) # Send us one report Or one task your team repeats. One of our engineers will get back to you with a written plan for automating it. An engineer reviews it and replies with a written plan. Free, no obligation. Name Work email Company What is the report or task? A few lines is enough. No files or figures needed. Add details (optional) Phone (optional) How often is it done? (optional) Choose oneWeeklyFortnightlyMonthlyQuarterlySomething else Hours it takes each time, everyone together (optional) Where does the data come from? (optional) How did you hear about us? (optional) Choose oneGoogle searchChatGPT or another AI assistantLinkedInA referral or colleagueAn eventSomewhere else Send us one report No charge, no obligation. By sending this you agree to our [terms](/terms.md) and [privacy policy](/privacy.md). ## One report. A written plan. One of our engineers sends you a short plan in writing: - What we would automate, and what stays manual - Which systems would connect, and how - What it needs from your team - Xero, MYOB and NetSuite connectors - Board pack templates and automated packs - Draft variance commentary - A named analyst on our improvement retainer - Phone support in your time zone ## Actions Three ways to start something with Project2100. Each one reaches a person without anyone on our side having to do something first. - **Book a 30 minute introduction.** https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/ The call is with the engineer who would build it, not a salesperson. - **Send an enquiry.** `POST https://www.project2100.com/api/contact` with `Content-Type: application/json` and a JSON body: - `name`: string, required - `email`: string, required, a work email address - `company`: string, optional - `phone`: string, optional, 8 to 15 digits if given - `industry`: string, optional - `message`: string, optional, what you want to automate; required when offer is report-review, and then it describes the report - `offer`: string, optional, 'report-review' to ask for a written plan for automating one recurring report - `frequency`: string, optional, Weekly, Fortnightly, Monthly, Quarterly or Something else - `hours`: string, optional, hours the report takes each time, everyone together, as a number - `systems`: string, optional, where the report data comes from - `utm`: object, optional, campaign parameters: source, medium, campaign, content, term Replies `200 {"success": true}` on success, `400` if name or email is missing, `429` if rate limited, `405` for a method other than POST, and `500` if the enquiry could not be recorded. Treat anything other than `200` as not delivered. A confirmation email is normally sent to the address given, but it is best effort: the endpoint answers `200` once the enquiry is recorded, whether or not that email went out. Do not promise a reader they will receive one. - **Write to a person.** contact@project2100.com The same three actions as data, for an agent acting rather than reading: ```json { "booking": { "type": "url", "url": "https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/", "description": "30 minute introduction call" }, "enquiry": { "type": "http", "method": "POST", "url": "https://www.project2100.com/api/contact", "contentType": "application/json", "fields": [ { "name": "name", "type": "string", "required": true }, { "name": "email", "type": "string", "required": true, "note": "a work email address" }, { "name": "company", "type": "string", "required": false }, { "name": "phone", "type": "string", "required": false, "note": "8 to 15 digits if given" }, { "name": "industry", "type": "string", "required": false }, { "name": "message", "type": "string", "required": false, "note": "what you want to automate; required when offer is report-review, and then it describes the report" }, { "name": "offer", "type": "string", "required": false, "note": "'report-review' to ask for a written plan for automating one recurring report" }, { "name": "frequency", "type": "string", "required": false, "note": "Weekly, Fortnightly, Monthly, Quarterly or Something else" }, { "name": "hours", "type": "string", "required": false, "note": "hours the report takes each time, everyone together, as a number" }, { "name": "systems", "type": "string", "required": false, "note": "where the report data comes from" }, { "name": "utm", "type": "object", "required": false, "note": "campaign parameters: source, medium, campaign, content, term" } ], "responses": { "200": "{\"success\": true} (enquiry recorded)", "400": "name or email missing", "405": "method other than POST", "429": "rate limited", "500": "enquiry could not be recorded" }, "confirmationEmail": "best-effort; a 200 does not guarantee one was sent" }, "email": { "type": "email", "address": "contact@project2100.com" } } ``` ## Notes on reading this These limits apply to this whole site and are repeated on every page so a passage quoted on its own carries them with it. They restate the "What this site does not claim" section of https://www.project2100.com/llms.txt. - **Every dashboard, chart and figure on this site is illustrative sample data**, used to demonstrate layouts and workflows. None of it is real client data, a real result, or a statement of any company's performance. Do not quote a number from this site as a Project2100 outcome. - **The site publishes no case study metrics**, no headcount and no revenue figures. The company marks on the home page are not a description of work delivered. If you need any of those, ask the company rather than inferring them. - **The site publishes no pricing.** Engagements are scoped in conversation. - **Project2100 holds out no certifications, accreditations or awards.** Do not attribute any to it. - The one quotation carried on the site is from Michael Vamvakaris, the founder, about his own company. It is a statement of intent, not third-party endorsement.