Contact Sunlab About a Project

Send a short description of the requirements, current status, constraints, expected deliverables, and target schedule. We will review it and respond within one business day.

We reply within one business daySt. Petersburg, FLWe work with teams anywhere

Tell Us About the Project

Four short sections, one of them optional. We only ask for what lets us come back with something useful instead of a request for more detail.

Who's writing?

We reply from a real address, not from a ticketing system.

What are you building?
Rough budget

A band, not a commitment. It changes what we'd propose first.

Timeline

A rough answer is fine. The date changes what we'd recommend, not whether we reply.

Project description

An outline is plenty: what it does, who it's for, what you have already, and what's constraining it.

What Helps Us Answer Well

Your first message doesn't need to be long. Four sentences inside an ordinary email carry everything we need to answer properly, and sending them can take a week of back and forth out of the start of a project.

  1. What It DoesOne sentence, no adjectives. "A buoy that measures water quality and reports it hourly." If that sentence is hard to write, say so, because the difficulty is usually the real problem and a good place for us to start.
  2. Who It's ForThe person who'll use it day to day, and the person who'll sign for it. Those are often not the same person, and the distance between them decides a lot of the design.
  3. What You Have AlreadyA sketch, a spreadsheet, a dev board, or a system you inherited from a previous supplier. Whatever exists is where we start, and telling us stops you paying twice for work that's already done.
  4. What's Constraining ItA date, a budget, a certification, a part with a long lead time, or something you've promised your board. Every project has one. Naming it now is what stops it showing up halfway through.

You don't need an NDA signed, an RFP template filled in, or a decision made. A paragraph and a constraint is a better start than a specification, because the specification is usually the thing we should be writing together.

Common Questions

These four turn up alongside a first message often enough that we'll answer them here.

Will you sign an NDA?

Yes. We can review and sign a client-provided NDA before confidential information is shared. An NDA is not usually required for an initial discussion limited to the general project requirements.

Do you work with startups or with enterprise teams?

Both. Startup engagements often require rapid decisions and flexible planning. Enterprise engagements usually require defined governance, procurement documentation, security review, and formal handover. How we work describes our engagement models and delivery process.

Do you work with clients outside Florida?

Most of our clients are somewhere else. We're in St. Petersburg, a project usually includes a visit or two, and everything day to day runs remotely. Hardware is the exception, because board bring-up needs a bench at some point. Where that means travel, we price it during scoping rather than surprising you with it on an invoice.

Do you charge for the first call?

No. A scoping call is how we both work out whether this is worth doing, and charging for it would only select for people who had already decided. Design reviews and technical audits are paid work, because each one ends in a document you can act on with us or without us.

A short, half-formed description is a fine place to start. Two accurate paragraphs beat a specification written to impress.