The ten ideas
All start without financial questionnaires, CSVs, bank logins or user-connected integrations. The optional follow-up comes after the result.
01Customer enquiry check
Show broken enquiry links, hard-to-find contact routes and demanding public forms, with screenshots and fixes.
- User enters
- A business website URL
- Who it helps
- A service-business owner who wants customers to reach the right person easily.
- What they get
- A short journey report: where to enquire, links that fail, mobile friction and the three clearest fixes. Each finding points to the page evidence.
Illustrative resultYour Contact link returns 404. The working enquiry form is three clicks away.
Smallest build, business fit and limits
- Smallest MVP
- Fetch the homepage and linked contact page; check public links and form labels at desktop and mobile sizes. No form submission. Estimated prototype: 2 to 3 engineering days.
- Business fit
- OI: a concrete introduction to improving enquiry forms, booking routes and lead handoffs.
- Be clear about
- A long form may be intentional. Public inspection cannot prove whether a message reaches an inbox, gets answered or converts.
02Website-to-finance plan
Get a tailored month-end checklist and questions for an accountant, based on the business model the site shows.
- User enters
- A business website URL
- Who it helps
- A founder who needs a starting point for organising finance, without preparing files first.
- What they get
- A plain business-model summary, a month-end checklist and five questions to discuss with an accountant. Label the inferred model and link its public evidence.
Illustrative resultYour site sells subscriptions. Here are the recurring-billing and month-end records to discuss with your accountant.
Smallest build, business fit and limits
- Smallest MVP
- Read the homepage plus one service or product page; map visible business models to accountant-reviewed checklists. Ask for one-click confirmation only if the model is unclear. Estimated prototype: 1 to 2 days.
- Business fit
- Godfrey: an optional conversation about bookkeeping, cash planning and reporting using the checklist the founder already received.
- Be clear about
- This is a suggested plan, not a health score. A website cannot show whether the books are reconciled, how much cash exists or which taxes are due.
03Business email setup check
See what published mail records show and which setup issues need attention, in plain language.
- User enters
- A company domain
- Who it helps
- A small-business owner worried about enquiries or invoices sent by email.
- What they get
- MX, SPF and DMARC record findings, readable explanations and a fix list with source records and check time. Report unknowns explicitly.
Illustrative resultNo MX record was found for this domain at the time checked. Here is what that means and what to verify.
Smallest build, business fit and limits
- Smallest MVP
- DNS lookups and a narrow set of record checks. No email sending, mailbox login or automatic DNS edits. Estimated prototype: 1 to 2 days.
- Business fit
- OI: a small email-operations setup engagement. Easy to demonstrate, but established lookup tools make this a crowded category.
- Be clear about
- Records alone do not establish inbox placement, working mailboxes or successful delivery. Do not report DKIM as missing by guessing its selector.
04Pricing clarity check
Flag unclear currency, billing periods, seat minimums and conflicting offers before they confuse a buyer.
- User enters
- Your public pricing-page URL
- Who it helps
- A SaaS or service-business owner reviewing how they explain prices.
- What they get
- A marked-up list of visible ambiguities, the exact supporting text and suggested clarifications. Separate missing public information from an actual contradiction.
Illustrative resultThe card says per month, but the footnote requires an annual commitment. Put both together.
Smallest build, business fit and limits
- Smallest MVP
- Read one pricing page and one linked terms page. Use explicit extraction plus a small set of clarity checks. Estimated prototype: 1 to 2 days.
- Business fit
- Godfrey and OI: clearer billing requirements and a scoped billing-process review.
- Be clear about
- A public page cannot reveal negotiated rates, invoices, tax treatment or revenue leakage. A hidden price may be a deliberate sales choice.
05Refund policy clarity check
Find missing or contradictory return and cancellation instructions, with the relevant page text beside each finding.
- User enters
- A shop or public policy URL
- Who it helps
- An ecommerce operator trying to reduce avoidable customer questions and disputes.
- What they get
- A coverage checklist for time windows, exclusions, how to request a return and who pays return shipping; show conflicting public instructions.
Illustrative resultThe FAQ says 14 days, while the linked policy says 30. Review which promise applies.
Smallest build, business fit and limits
- Smallest MVP
- Read the policy and one linked FAQ or product page. Compare statements and show wording to review. Estimated prototype: 1 to 2 days.
- Business fit
- Godfrey financial operations and OI customer-support workflows: clearer refund handling and handoffs.
- Be clear about
- This checks clarity, not legal compliance or enforceability. It cannot observe actual refund execution, disputes or chargeback rates.
06Invoice and quote check
See missing information and arithmetic checks, with every finding tied to the relevant line.
- User enters
- One redacted text paste; a public template link also works
- Who it helps
- A freelancer or small-business operator checking a draft before sending it.
- What they get
- Missing identifiers, unclear dates or payment terms, arithmetic differences and an editable correction checklist. Explain the calculations.
Illustrative resultThe listed line totals add to 450, but the subtotal shown is 480. Check the difference.
Smallest build, business fit and limits
- Smallest MVP
- Plain text and public text templates only; simple field extraction and deterministic arithmetic. No PDF uploads or OCR at first. Estimated prototype: 1 to 2 days.
- Business fit
- Godfrey: useful finance support before a user is ready to share their books.
- Be clear about
- Redact names, addresses, bank details and private references; prefer local processing. This does not certify a statutory invoice, tax rate or transaction.
07Subscription cost explainer
Turn published fixed and per-seat rates into clear monthly and yearly scenarios, with the commitment terms visible.
- User enters
- A software pricing URL; seat count is optional
- Who it helps
- A founder or operations lead comparing a software purchase.
- What they get
- A plan comparison using source prices, an editable seat count and commitment periods. Unknown usage fees, taxes and discounts stay unknown.
Illustrative resultAt the published per-seat rate, here is the cost for five seats, shown separately for monthly billing and annual commitment.
Smallest build, business fit and limits
- Smallest MVP
- One pricing page, flat-rate and per-seat models, arithmetic and source links. Mark unsupported pricing clearly. Estimated prototype: 2 to 3 days.
- Business fit
- Godfrey FP&A and OI operations: a starting point for reviewing a proposed software purchase.
- Be clear about
- This is a price scenario, not a spend audit. It cannot see current subscriptions, utilisation, negotiated discounts or future usage. Annual commitment is not monthly flexibility.
08Finance automation starter map
Get three suggested workflows and proposed human review points from the enquiry, booking or order journey the site shows.
- User enters
- A business website URL
- Who it helps
- A founder who wants concrete ideas before agreeing to an operations review.
- What they get
- Three workflow sketches, the visible evidence behind each, an appropriate review point and what must be confirmed internally.
Illustrative resultA visible booking flow suggests a booking-to-client-intake handoff to investigate. First confirm how it works today.
Smallest build, business fit and limits
- Smallest MVP
- Read three public pages and select from a reviewed workflow library. Label every unverified step as a suggestion. Estimated prototype: 2 to 3 days.
- Business fit
- OI: an optional workflow-discovery call with a useful starting brief.
- Be clear about
- Do not infer the internal tool stack, staff effort, manual workload, hours saved or ROI. A public booking form does not prove a manual back office.
09Supplier bank change check
Spot concerning wording and missing verification steps, then get a callback checklist before acting.
- User enters
- One short, redacted request text
- Who it helps
- An owner or finance operator who receives a request to change payment details.
- What they get
- Wording that deserves attention, missing evidence and a trusted-contact verification checklist. Provide a neutral draft reply for human review.
Illustrative resultThis request changes bank details and asks for urgency. Verify through an existing trusted contact route before acting.
Smallest build, business fit and limits
- Smallest MVP
- Text-only checks against a reviewed verification checklist, preferably in the browser. No links opened, attachments processed, emails sent or payments initiated. Estimated prototype: 1 to 2 days.
- Business fit
- Godfrey financial operations and OI approval workflows: a useful entry point to reviewing payment controls.
- Be clear about
- Remove real bank numbers and private identities before pasting. Never label a request safe or fraudulent, authenticate an account or approve a payment. Verification requires an independent trusted channel.
10UK company filing status
See published accounts and confirmation-statement due dates, overdue flags and the source record in one brief.
- User enters
- A public Companies House link or company number
- Who it helps
- A UK limited-company owner or accounting firm checking a company's public filing record.
- What they get
- A dated public-record summary with source links and clearly separated accounts and confirmation-statement information. Show unavailable fields as unknown.
Illustrative resultThe public record shows separate dates for accounts and the confirmation statement. Here are both, linked to the register.
Smallest build, business fit and limits
- Smallest MVP
- Read the Companies House company-profile endpoint using a backend developer API key. No user login or filing action. Estimated prototype: 1 to 2 days once developer access is ready.
- Business fit
- Godfrey's UK offshore service: help preparing records for the responsible UK adviser. Local filings and sign-off remain with the appropriate practitioner.
- Be clear about
- UK entities only. Public filing status is not tax status, creditworthiness, solvency or accounting quality. The official register and its free reminders are the cheaper baseline.
Keep the first version small
- Give the result first. One input, one action, a readable report. Offer saving, sharing or a conversation afterwards. Avoid a compulsory email gate.
- Show what was observed. Link each finding to a page, quoted text or public record and show the check time. Keep suggestions and missing evidence separate. A blocked or script-only page is “not checked”, not “broken”.
- Use the cheapest reliable method. DNS, arithmetic and field checks do not need an LLM. Use a small model only for a bounded explanation or classification. Cap pages read, cache public snapshots and offer a fresh check. Do not send private pasted text to a model without the user’s permission.
- Start with the narrow scope described above. Prototype estimates exclude accountant review, security hardening and support. Safe URL fetching and handling blocked pages are launch requirements; a public scanner must not fetch private network addresses or submit customer forms.
Seven-day proposal for the enquiry check: first review 15 controlled or permissioned sites against a manual walkthrough. Then aim for 30 relevant owners to try it through existing permitted distribution: 10 finish, 5 save or act on the report, and 2 ask for a scoped improvement conversation. Treat these as proposed thresholds, not observed results.
Godfrey alternative: show the finance plan to 10 relevant owners. Continue if 7 recognise their business model, 5 identify an action they intend to take and 2 request a conversation about the work. If the checklist feels generic, improve it before adding data uploads.
No outreach, ads, scans of third-party sites or paid activity were performed for these proposals. Demand and willingness to pay are unmeasured. Track completed results, real use, qualified conversations and paid engagements separately; keep financial text and contact details out of analytics.
What public information can establish
A website can show published prices, promises, contact routes and business context. DNS and official registers can supply specific public records. None of those reveal cash balances, reconciled books, profit margins, tax liabilities or actual staff workload.
Each proposed report needs a useful output within that boundary. The Godfrey service offering supports the finance and accounting fit; OI workflow work is the proposed follow-up for the enquiry and operations tools.
Primary pages checked 24 October 2026. These sources support the inputs and limits, not demand for a new product.