Let your people do the work you hired them for.

We build software for field service businesses that takes the re-typing and chasing off your office and crews, and works with the tools you already use. Fixed price, agreed in writing.

A video call with me, Jeff Taylor. We go through how a normal day runs, and I tell you whether an audit would pay for itself.

Tallyfield's owner dashboard: days from work to invoice, tickets awaiting approval, tickets returned to technicians, and approved work not yet invoiced, by customerTallyfield on a phone: a technician's tickets, the returned ones first with the supervisor's reason
Screens from Tallyfield, a field-service demo we built. The company and data are invented.

What the re-typing costs, on your numbers

Two minutes, free, and nothing you enter leaves this page.

Step 1 of 9. Is the same job typed into more than one system?

Choosing an answer moves on to the next question.

What it looks like in your business

Real screens from Tallyfield, a field-service demo we built, on invented data. Yours is fitted to your work.

For your crews

The job is logged once, on a phone

Customer, site, hours and materials go in at the job. Nobody types them again back at the office.

Tallyfield on a phone: a technician starting a new field ticket with customer, job site, work date and work performed

For the office

Invoices are built from approved work

Once a supervisor approves the tickets, the invoice is ready line by line, and it exports straight to your accounting.

Tallyfield: an invoice built from two approved field tickets, labor and material lines with totals, and a Download CSV button

For the owner

You can see the money that is stuck

Work done but not billed, how long invoices take, what is waiting on approval: one screen, updated as the work moves.

Tallyfield's cash-cycle dashboard: median time from work to invoice, tickets awaiting approval, approved work not yet invoiced, and unbilled work by customer

Three ways to stop the re-typing

An off-the-shelf app, no-code automations and custom software, compared
An off-the-shelf appHow it fits your workYour team changes how it works to fit the appWho fixes itThe vendor, on their scheduleWho owns itThe vendorWhat it costsA monthly fee per user
No-code automations between your appsHow it fits your workEach step depends on two other apps staying the sameWho fixes itWhoever set it up, if they are still aroundWho owns itSpread across the apps you subscribe toWhat it costsPer task, plus the time to keep it running
Software built around your businessHow it fits your workBuilt to how your crews and office already workWho fixes itUs, under care, or your own teamWho owns itYou: the code and the dataWhat it costs$3,000 audit, then a fixed price, typically $20,000 to $30,000

How it works, and what it costs

Fixed prices, written down before anything starts.

  1. 1. Free call

    Free, 30 minutes

    We go through how a normal day runs. I tell you plainly whether an audit would pay for itself.

  2. 2. Deep audit

    $3,000, fixed

    We sit with your team, map where work is typed twice, and write down what to build first and its fixed price. Go ahead with the build within 60 days and the $3,000 comes off the build price. You keep the plan either way.

  3. 3. Build

    $20,000 to $30,000, fixed

    Built one piece at a time on a live preview you can use on your phone. Nothing moves on until you approve it.

  4. 4. After launch

    30 days of support included

    Then care, priced to what you run: nightly tests, data checks and fixes. Or a strategic partnership, where I work as your fractional CTO and we scope it together.

Scope is frozen in writing at the end of the audit. Anything outside it is quoted as a written change request before work starts, and if the agreed scope takes longer than planned, that's our cost. You can stop after the audit and keep the plan.

Results from my past work

  • 75%less time spent processing documents, with an automated PDF-to-invoice system
  • 22%lower hedging costs for an energy provider, from a power load-shaping model
  • 40%more productive sales reps, with a custom CRM
  • 30%better customer retention, from the same CRM
  • 90%of the manual work automated across 300+ commodities at a pricing agency

Examples of the work we deliver

Each is a complete build, taken from brief to release through the same process every project goes through.

These were built for practice clients we created to test our process. The businesses, people and data are synthetic.

Fernbrook on a phone: today's round of repair visits by morning, afternoon and evening, each with customer, address, bike and problems
Mobile bike repairFernbrookCalls become jobs on a waiting list, the owner plans the day's round on a phone, and takings add up by week.
Readyroom: a firm's client engagements, each with its document request list, status and how many items are accepted
Accounting firmReadyroomClients upload documents against a request list, and staff accept each item or send it back with a reason.
Larkspur on a phone: the managers' list of kitchen phones, who set each one up and when it was last used
RestaurantLarkspurOpening and closing checklists and food-safety temperature logs on kitchen phones that managers set up and track.

From my own work: RNG RFP, a marketplace I built for requests for proposals in renewable natural gas and renewable energy projects.

Questions

What does Auxelion do?

We build software for field service businesses. A job is entered once, on site, and from there it reaches scheduling, invoicing and the owner's dashboard without anyone typing it again.

How much does it cost?

The deep audit is $3,000, and it comes off the build price if you go ahead within 60 days. A typical build is $20,000 to $30,000 at a fixed price. Every build includes 30 days of support. Care and strategic partnership after launch are priced to what you need.

Is the first call free?

Yes. It is 30 minutes, and its job is to decide whether an audit is worth it for you. If it isn't, I'll say so on the call.

Do we have to replace the software we use?

No. Where your current tools do the job, we build around them and remove the manual steps between them.

Who is this a poor fit for?

If an off-the-shelf app already fits how your business works, buy the app. I'll tell you on the call if that's the case.

Who owns what you build?

You do. The code is yours, and so is your data.

What happens to our data?

When we hold your data, we do it under a written agreement, and at the end of the engagement we return it or delete it, whichever you choose.

Jeff Taylor, founder of Auxelion

A note from Jeff

I've been building software for 15 years, most of it for energy and finance companies where a wrong number costs real money. I started Auxelion in 2018 to bring the same rigor to businesses that run on job sheets and spreadsheets.

When you book a call, you talk to me. I'll ask how a normal day goes: where things get typed twice, chased or fixed by hand. If an audit wouldn't pay for itself, I'll tell you on the call.

Jeff Taylor

Founder, Auxelion

Houston, Texas