RAISE Tech

RAISE Tech  ·  Custom AI Tools  ·  Discovery

Custom AI Tools discovery

Interested in a custom tool? A few questions so our conversation starts with your actual work instead of a blank page. Rough answers are fine.

Before you start

There are no wrong answers here, and you do not need to know what is technically possible. That is my job. What I need from you is the shape of the problem.

Please do not send client records, case notes, or any identifying information about the people you serve. Describe the kinds of information involved instead. If we go forward, we handle the real material properly and with an agreement in place.

Two ways to build

You do not have to choose. This is here so you can see the two shapes a build can take, and so one of the questions below makes sense when you get to it.

Light Lane

A working interactive tool built specifically for your context, delivered ready to use. No logins, no database. Usually one to three weeks once the scope is agreed, depending on how quickly you review drafts.

For example: a funder communication toolkit for a development team, or a daily assistant calibrated for one professional's specific work.

Platform Lane

A full working application with its own logins, database, and user accounts. Your timeline is set in your written scope.

For example: a trauma-informed intake and screening tool with staff login and case tracking, or a reentry employment navigator with participant progress tracking.

Your details

The essentials

Eight questions. Take as much space as you need.

One or two sentences is enough.

Walk me through the current process, even if it is messy. Messy is useful.

Roles are more useful than names. Tell me who they are and what their day looks like.

Categories, not contents. For example: client names and dates of service, or grant budget figures.

If yes or not sure, tell me a little about what kind. This changes how the tool gets built, so it matters more than almost anything else on this form.

Be as concrete as you can. What is different for the people using it, and for the people they serve?

A grant deadline, a staff change, a program launch. The reason matters as much as the date.

Include anyone who does this work day to day, not only decision makers. The people closest to the task usually know the details that shape the tool, and they are often not the person filling out this form.

A rough number or a range is fine. This tells me what is realistic to propose, and I would rather know now than design something you cannot fund.

Answer these if you can

These help me prepare before we talk. If you do not know, or they do not apply to you, skip them. We can cover any of them on the call.

If you are not sure, say so. This is one of the things that decides which lane fits.

The two lanes are described near the top of this form. Not sure is a completely fine answer.

Anything counts. Software you bought, an AI tool someone experimented with, a spreadsheet system, or a change to how the work gets done. What went wrong is often the most useful thing on this form.

What happens after you send this

I read it and come back to you within two business days, and we schedule a time to talk. Plan on about forty five minutes.

On that call I will ask about a few things that are harder to answer in a form, and I may suggest tool or design ideas that are new to you. That conversation is the heart of where the tool gets designed, so bring your questions too.

After that, I will send you a written approach and a price for the build. Nothing gets made until you have seen it and agreed to it. Once we start, we stay in touch, because some of the best decisions come from watching the tool take shape.