Pushbuild

A pile of documents in, a clean spreadsheet out.

Sometimes you do not need a system, you need one batch turned into rows. Send us the PDFs, scans, photos or handwritten pages and we return a spreadsheet laid out the way you asked, with every doubtful entry marked and a list of anything we could not read. The scope is agreed in writing, and you approve a sample before the full batch.

Tell us what you needSee typical projects

You describe it. We build it.

PDFs and scansClean spreadsheetPhotos of pagesMarked doubtsHandwritten formsCounts in and outConvert and checkbuilt by Pushbuild

Sound familiar?

What we hear from businesses before a project like this starts.

  • We have a box of paper forms that has to be in a spreadsheet, and nobody here has the time to type them.
  • There is one batch of PDFs to get through, and we do not want to buy a system for it.
  • Handwritten log sheets need to become something we can search and add up.
  • We pasted a scanned table into Excel and it came out as one block of text.
  • Each document has to be matched to a set layout and a formula sheet, and doing it by hand is slow.
  • We typed a batch in ourselves and found the mistakes weeks later.
  • Our documents are in Spanish or Hindi, and our usual typist cannot read them.
  • The records came in a format our software cannot import.

What buyers usually need

The requests that come up most often for this kind of work, and what each one takes to work properly.

01

PDFs into a sheet

Tables, invoices, forms or statements from PDFs placed in the columns you specify, one row per record.

02

Scanned and photographed pages entered

Scans and phone photos read and entered with dates and numbers in one style, blank and duplicate rows flagged, and unreadable words marked rather than guessed.

03

Handwriting into rows

Handwritten pages entered after a test on a sample, with every doubtful word highlighted so you can see exactly where to look.

04

Your own layout and formulas

Data placed in the workbook and formula sheet you already use, so totals and reports work as soon as you open it.

05

Records moved between formats

An export from one system, a Word table or a web page turned into a clean CSV or import file for the software that has to read it.

06

Documents in other languages

Spanish, Hindi, French or another language you name, tested on your sample first, with a note of how well each one reads.

07

Counts and a list of problems

Records counted in and rows counted out, and a list of unreadable pages with the page image beside each.

08

Output where you work

Excel, Google Sheets, CSV, or an import file for your accounting software or CRM.

Tools that come up most: Excel, Google Sheets, CSV, Word, PDF, OCR, Airtable, Python, QuickBooks and Xero import files.

What you get

Concrete pieces, each one something you can open and check when it's done.

PDFs and scansClean spreadsheetPhotos of pagesMarked doubtsHandwritten formsCounts in and outConvert and checkbuilt by Pushbuild

A sample first

A small slice of your batch converted and sent to you, with the column list and the date and number styles agreed before the rest is done.

Sample file, column list

The conversion

The full batch entered into your layout, one row per record, with the source file and page on every row.

Excel, Google Sheets, CSV

Checks on the numbers

Totals added up against the source, dates and numbers made consistent, duplicates and blank rows flagged.

Validation rules, comparison totals

Doubtful entries marked

Anything hard to read is highlighted and listed, never quietly filled in with a guess.

Highlighted cells, query list

A list of unreadable pages

Each page we could not read, with its image beside the note, so you can decide what to do with it.

Page images, a short list

Delivery and a record

The finished file, the record counts in and out and a short note of the choices made, so any row can be explained later.

Counts sheet, notes

Careful handling of the files

Files passed through a folder you share, the tools that see them named in the scope, and the files removed from our side once you confirm receipt.

Shared folder, written handling note

Typical projects

Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.

Example package

Small batch to a sheet

A few dozen documents or pages turned into a sheet, with a list of anything unclear.

You get

  • Column list agreed before starting
  • Every record entered with its source page
  • Doubtful entries highlighted
  • The finished file in Excel, Sheets or CSV

Example package

Large batch, sample first

A bigger batch, started with a sample you approve.

You get

  • A sample approved before the full run
  • Column list and formats agreed in writing
  • Counts of records in and rows out
  • A list of pages that could not be read

Example package

Handwritten and scanned pages

Paper records entered into a searchable, consistent sheet.

You get

  • A test on your sample pages first
  • Dates and numbers in one style
  • Blank and duplicate rows flagged
  • Unreadable words marked for you to resolve

Example package

Into your template

Data placed in the workbook, formula sheet or import file you already use.

You get

  • Your layout and formulas left as they are
  • Data placed in the right cells
  • A check that your totals work
  • A note of anything that did not fit

How we approach it

The habits that keep this kind of project from going wrong.

1

Sample before the full batch

You see a slice of the real result and agree the columns and formats before we do the rest.

2

Doubt stays visible

What we cannot read is marked, not guessed. You decide what goes in.

3

Count everything

Records in the source and rows in the sheet are counted and compared, so a missing page shows up.

4

Your files stay yours

We say in the scope where the files go and who sees them, and remove them from our side when you confirm you have the results.

How we work

You know what you're getting before work begins, and you see it working at every milestone.

  1. You describe it

    Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.

  2. A written scope

    We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.

  3. Milestones you review

    The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.

  4. Handover and a 30-day fix window

    You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.

What shapes the scope

  • How many documents or pages
  • Typed, scanned, photographed or handwritten
  • How many fields in each record
  • Languages involved
  • How soon you need it

Always included

  • A written scope before work starts
  • Milestones you review and sign off
  • Documentation and a walkthrough at handover
  • A 30-day window for fixes, at no charge

Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See example builds.

Questions people ask first

Is this a typing service?

For a one-off batch, in effect yes: we convert it and check every uncertain entry. If documents keep arriving every week, we can build a system that reads them instead, so the next batch needs no one. That is the PDF data extraction page.

How do I know the entries are right?

You approve a sample first, totals are checked against the source, and every doubtful entry is marked. You also get a count of records in and rows out.

How well can you read handwriting?

Handwriting varies a great deal. We look at a sample first and tell you how much of it reads cleanly. Words we are not sure of are marked in the sheet instead of filled in.

Is it worth it for a small batch?

Tell us the number of pages. If doing it yourself or a typing service would suit better, we say so.

Can you work with other languages?

Yes, for languages such as Spanish, Hindi and French. We test your sample first and tell you in the scope how well each one reads.

Is my data private?

You send files through a folder or link you control. The scope names the tools that see them, and we remove the files from our side when you confirm receipt. If the files are medical or financial, tell us early so the scope covers it.

What format do I get?

Excel, Google Sheets, CSV, or an import file for your accounting software or CRM, laid out the way you specified.

How long does it take?

It depends on the number of pages and how readable they are. Once we have seen a sample, the scope gives an estimate for the full batch.

What happens after handover?

If entries do not match the source in the 30 days after handover, we correct them at no charge. After that, further batches are scoped the same way and agreed with you before we start.

Do it once, we automate it. Show us the job one time and it runs on its own after that, in the tools you already use.

Tell us what you need built.

Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.

hello@pushbuild.com

(617) 299-8887