Capabilities

Software for the problems your team works around every week

Kirk & Co. designs and builds software around the way a business actually operates: the records it keeps, the steps work passes through, and the people who need to see each part.

Start from the problem

Choose the one that costs you the most

Each opens the kind of system that usually fixes it, what it replaces, what it could include, and where you can see one working.

01

We re-enter the same information in multiple places.

Likely system
A shared customer and job record
What it replaces
Typing a customer’s name, address and job into the quote, the schedule and the invoice separately, then fixing the copies when they disagree.
What it could include
  • One record per customer, entered once
  • Quotes, jobs and invoices that read from it
  • Imports from the spreadsheets you keep now

Working example

Horizline keeps one record from the first call to the paid invoice. Converting a lead copies its details to the new client and links the two.

Read the Horizline case study

Tell us where you retype things

02

Nobody can see the current job status.

Likely system
A job board everyone reads from
What it replaces
The whiteboard, the “where are we on this?” text thread, and the one person who always has to be asked.
What it could include
  • Stages, owners and due dates on every job
  • Views for the office, the crew and the owner
  • What is waiting, and on whom

Working example

Horizline’s Jobs list shows every job, who runs it, how many of its tasks are done and what it is worth.

See the screens

Tell us how you track jobs today

03

Our process lives in one employee’s head.

Likely system
Workflow software with your steps written in
What it replaces
Steps that depend on memory, approvals by text message, and the week nobody can cover when that person is out.
What it could include
  • Steps and hand-offs in the order your team works
  • Rules for approvals and exceptions
  • A record of who did what, and when

Working example

In Horizline each business names and orders its own pipeline stages, and the activity log shows who changed what.

About Horizline

Walk us through the process

04

Our tools do not communicate.

Likely system
Connections between the tools you keep
What it replaces
Copying the same details from one tool into another by hand, and checking later that both still match.
What it could include
  • Links to accounting, payment, email and calendar tools that allow them
  • Records created from your web forms
  • Reminders tied to real events

Working example

Horizline connects to a business’s own Stripe account, and each client’s invoices are filed against that client.

About Horizline

List the tools you use

05

Basic reporting requires rebuilding a spreadsheet.

Likely system
A dashboard drawn from the records
What it replaces
Monday-morning spreadsheet assembly, and totals that change depending on who ran them.
What it could include
  • The few numbers that drive your decisions
  • Filters by crew, service, customer or period
  • A path from each total to the jobs behind it

Working example

Horizline’s Overview shows payments received, the amount outstanding, the open pipeline and open jobs, straight from the records.

Read the Horizline case study

Tell us which numbers you need

06

Customers or field staff keep calling the office for updates.

Likely system
Sign-ins for your crew and your customers
What it replaces
Status phone calls, schedules sent by text the night before, and documents passed around as attachments.
What it could include
  • Staff who see the work assigned to them
  • Status, documents and messages for each job
  • Pages that work in a phone’s browser

Working example

In Horizline each team member has their own sign-in with the access you choose, and contacts, the pipeline and jobs fit a phone’s screen.

About Horizline

Tell us who keeps calling

The systems behind the answers

Six kinds of software, usually combined

A single project often joins several of these into one system for one business.

01

Internal operations systems

The system your office runs on: customers, jobs, schedules and statuses in one place, with screens for the office, the field and the owner.

ReplacesThe whiteboard, the shared spreadsheet and the “who has this?” text thread.

02

Workflow and process software

Software that walks work through the steps your business already follows, with the hand-offs, approvals and exceptions written into the tool instead of kept in someone’s head.

ReplacesSteps that depend on memory, approvals by text message, and forms passed around by email.

03

Customer and staff portals

Secure pages where customers check status, sign, upload or pay, and where staff see only the work assigned to them.

ReplacesStatus phone calls, documents sent as attachments, and staff asking the office what is next.

04

Reporting and decision dashboards

The handful of numbers you check every week, drawn straight from the records your team already keeps, so the answer is current when you ask.

ReplacesMonday-morning spreadsheet assembly, and totals that disagree depending on who ran them.

05

Automation and integrations

The repetitive steps between tools, handled by the system: records created from forms, reminders sent at the right step, and details passed to accounting or a calendar without retyping.

ReplacesCopying the same details from one tool into another by hand.

06

Product and web application development

Full web applications people sign in to, and public tools such as calculators and searchable databases. Horizline began this way, as Kirk & Co.’s own internal system.

ReplacesAn idea that has outgrown a spreadsheet, a form builder or a plug-in.

How a project runs

Understand the work first. Then build the system.

Strategy, design, development and support stay with one builder from the first conversation on. Each phase ends with something you can hold; the examples use sample data.

  1. Phase 01

    Understand

    Talk with the people who do the work—the office, the field, the owner—and trace how a job actually moves: where requests arrive, what gets typed twice, where things wait.

    Discovery notesSample
    • Requests: phone, web form, texts to the owner
    • Quote typed in a document, then retyped for the invoice
    • Crew learns the schedule by text the night before
    • Name and address typed 3 times

    You getA plain account of how work moves today, and where it breaks down.

  2. Phase 02

    Map

    Draw the system before building it: the records you keep, the stages work passes through, who needs to see what, and which steps should happen on their own.

    Data model and flowSample

    Customername, address

    Jobvisit, crew

    Invoiceamount, status

    InquiryQuoteApproveScheduleInvoice

    You getAn operations map and a defined first release you can review.

  3. Phase 03

    Build

    Design and develop in working increments, using your real terms and sample records, so you review usable software early rather than a long document.

    Release 0.3, for reviewSample

    Job J-207Scheduled

    CustomerMaria Alvarez

    VisitTue · 8:00 AM

    InvoiceDraft

    You getWorking software set up for your team, with existing records brought in where they can be.

  4. Phase 04

    Evolve

    Stay with it after launch: fix what gets in the way, adjust as the business changes, and add the next piece when it earns its place.

    After launchSample

    1.1Crew view shows the parts list

    1.2Owner report by service type

    1.3Reminder the day before each visit

    You getDirect support from Kirk & Co., the company that built it.

Questions before you write

Do we have to replace the tools we already use?

No. A system can connect to the accounting, payment, email and calendar tools that allow it, and bring in the spreadsheets you keep now. Often the tools are fine and the work between them is what needs fixing.

What do we get before anything is built?

A plain account of how work moves today, then an operations map and a defined first release you can review.

How soon do we see working software?

Early. It is built in working increments with your real terms and sample records, so you review usable software rather than a long document.

Who supports it after launch?

Kirk & Co., directly. The person who built it fixes what gets in the way and adjusts it as the business changes.

Is there a ready-made option?

If your work fits a CRM for contractors and service businesses, Horizline may be enough. It is Kirk & Co.’s own product, with a seven-day trial.

About Horizline

Start here

Tell us where work gets stuck.

The first step is a short message. You don’t need a specification, a budget or the right words for what you need.

  1. What to send

    A few sentences: what your team does, where work gets duplicated, delayed or lost, and the tools you use now.

  2. What happens next

    Elijah Kirk reads it and replies within one business day with a useful next step. Writing in commits you to nothing.

  3. Rather talk first?

    Write or call directly.

    kirk@kirk-co.com812-690-1753