The Reading desk
Send a project note to our Reading desk
Build the bench first, then ship. Write to us at 44 Park Road and one of the same small group here reads it — then replies with something concrete.
- Post
- 44 Park Road, Tilehurst, Reading, England
- [email protected]
- Hours
- Monday to Friday, 9:00 AM – 6:00 PM
A useful note, short form
Five clear sentences. The game in plain language, the engine you are leaning towards, team size, target platforms in priority order, and the one decision you are stuck on. A build link or store page helps but the note works without it.
What happens next
Your message reaches the Summerfield Goods Digital inbox, is read in the order it arrives, and gets a written reply — not a templated one — usually within a few working days.
If email suits you better than a form, write to [email protected] directly. The form simply asks for the handful of details that make the reply useful, and it is not a filter.
Send the project note
Tell us the decision you are stuck on — engine, slice scope, store page timing, Deck support, or something narrower. If you are earlier than that and working out whether the project is viable, tell us what you have.
Nothing you send is published or shared without asking you first, and we do not add senders to a mailing list. The privacy policy describes how long we keep a note.
Project note
What to include in a project note
The useful note is short. One paragraph on the game, in plain language. Add the four facts below and we can usually answer on the first reply instead of asking twice.
01 · Engine
The engine you are leaning towards
Or the honest fact that you have not chosen yet. That is a real answer and it changes what is worth saying back.
02 · Team
Team size and who is full-time
Two people on evenings reads very differently to four full-time. Say which one you are.
03 · Platforms
Target platforms, in priority order
PC first, Steam Deck support wanted, console later — the order decides the order we answer in.
04 · Decision
The one decision you are stuck on
Engine, slice scope, store page timing, Deck support, or something narrower. Name it and we skip straight to it.
Screenshots, a build link, or a store page URL are all welcome, but the note works without them. We would rather read five clear sentences than a press kit.
The desk in Tilehurst. Notes arrive here and are read in order.
How we reply, and what we help with
Replies come by email, usually within a few working days, and they are written rather than templated. If your question is one we have covered, we point at the page and add anything specific to your situation. If it is something we have not covered, we say that too, and we may ask a couple of clarifying questions before answering.
We do not run discovery calls. If a written reply is not enough, we will say so and suggest what would be.
We help with
- Engine choice — Unreal, Unity, Godot, GameMaker, or the honest case for staying put
- Prototyping sequence and vertical slice planning
- Steam page and wishlist sequencing
- Demo and early access decisions
- Steam Deck compatibility planning
We do not
- Write code, produce art, or port games
- Take a share of revenue on your project
- Publish sponsored content
- Act as an outsourcing contractor for art or code
- String a conversation along on a job we are not the right fit for
Being clear about this saves everybody a week. If your project needs a contractor for outsource work, we are not that, and we will say so on the first reply.
Where we are, and how we work
The desk is in Tilehurst, Reading, and the teams we work with are spread across the UK. That means the working rhythm is asynchronous: you write the note, we read it, we reply with something concrete, and you get back to the build.
There is no scheduled call to arrange and no window of the day where we are only reachable by phone. We do not ask for a phone number — email works.
At the desk
- Address
- 44 Park Road, Tilehurst, Reading, England
- Phone
- +44 118 436 8944
- [email protected]
- Hours
- Monday to Friday, 9:00 AM – 6:00 PM
Notes arrive at 44 Park Road. Replies leave by email, not by call.
What happens after you send it
-
It arrives
Read in the order it arrives, by the same small group.
-
We read it
Most notes get a reply within a few working days.
-
We reply
A note that needs a longer answer might take a little longer.
-
Not heard back?
Check the spam folder, then send a short follow-up. It happens.
A shorter path, if you have not read anything yet
If you are completely new to the site and not sure what to ask, read one of the three and send a note with the two decisions you are least sure about. That is enough for a genuinely useful reply.
Choosing a tool
Engine Guide
Four engines, honest trade-offs, and what to weigh when the choice is still open.
Read the guideBuild without a slice
Prototyping Workflow
How to get from a build that runs to a vertical slice that tells you something.
Read the workflowLaunch inside a year
Steam & Deck
Store page timing, wishlist sequencing, and what Deck support asks of you.
Read the guideStill not sure what to write? Send the note with one sentence about the game. We will ask the rest.